Custom Field Type Creation in Object-Based Database

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Object-based database systems struggle to accommodate unique business requirements beyond their predefined objects and configurations, limiting their ability to store specialized data such as employee fingerprints or security clearances.

Innovation Solution

A system for creating custom field types and objects within an object-based database, allowing administrators to extend existing data objects with new attributes and custom data types, such as user-defined numeric ranges, text lengths, and list elements, enabling flexible data object extensibility.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the system uses predefined objects and configurations, then the system structure is simple and easy to maintain, but the system cannot accommodate unique business requirements beyond standard entities

Engineering Contradiction:
Improveability to accommodate unique business requirementsVSAvoidsystem structure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments object definitions into templates and instances. Templates define the structure and validation rules for object types, while instances are actual data objects created from templates. This allows businesses to define custom object types with specific attributes and validation rules without complicating the overall system structure, as each custom object is a self-contained instance of a template.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent adds a template dimension to the object model. Instead of only having flat object instances, the system introduces templates as a higher-level abstraction that defines object structures. This dimensional addition enables extensibility by allowing users to create custom object types with specific attributes, validation rules, and configurations without modifying the core system architecture.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Adaptability or versatility

If the system allows extensive customization of objects and fields, then the system can meet diverse business needs, but the complexity of object creation and management increases

Engineering Contradiction:
Improvedata object extensibilityVSAvoidease of object creation
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The system performs preliminary action by providing pre-configured templates for common object types such as employees, customers, and products. These templates come with predefined attributes, validation rules, and data types already configured. Users can start with these ready-made templates and only customize what is specifically needed for their business, rather than creating everything from scratch, thereby reducing the operational complexity of object creation.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If the system stores specialized data types like fingerprints and security clearances, then the system covers more business scenarios, but the system loses its simplicity and standardization

Engineering Contradiction:
Improvedata type coverageVSAvoiddata structure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system applies local quality by allowing different data types and validation rules for specific attributes within objects, while maintaining a standardized overall structure. For example, an employee object can have a standard set of attributes (name, position, salary) with standard data types, plus specialized attributes (fingerprint data, security clearance level) with specialized data types and validation rules. This localized customization enables the system to handle diverse data requirements without compromising the standardization of the core object structure.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS9600136B1Data object extensibility
Publication Date: 2017.03.21 WORKDAY INC
  • US9600136B1 patent drawing
  • US9600136B1 patent drawing
  • US9600136B1 patent drawing

AI summary

A system for creating a custom field type comprises an input interface, a processor, and an output interface. The input interface is configured to receive an indication to create a custom field type. The processor is configured to validate a parameter of the custom field type. The output interface is configured to provide the custom field type for creating a custom field of a custom object.