Business Object Extension Field Propagation via Metadata
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Extending Enterprise Information Systems (EIS) is a time-consuming and resource-intensive process, as runtime extensions are not typically available, requiring complex modeling and testing of additional components during design time.
Innovation Solution
A system that allows users to create and propagate extension fields for business objects via a graphical user interface, storing metadata to enable backend propagation of these fields along data flows, thereby extending business objects without requiring development effort.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional EIS extension methods are used, then system reliability is maintained, but extension process time and resource consumption increase significantly
Solution Approach 1:
The system pre-establishes a framework where extension fields are defined with metadata before actual extension occurs. The propagation mechanism is pre-configured through data flow mappings, allowing extensions to be applied rapidly without re-modeling the entire system architecture each time.
Solution Approach 2:
Instead of creating entirely new business objects or re-modeling systems, the invention copies and reuses existing metadata structures and data flow patterns. Extension fields inherit the propagation logic of existing fields, allowing rapid deployment without duplicating entire extension mechanisms.
2Adaptability or versatility
If runtime extensions are implemented, then adaptability improves, but system complexity increases
Solution Approach 1:
The system introduces metadata as an intermediary layer between user extensions and the core business objects. This metadata layer abstracts the complexity of field propagation and data flow mappings, allowing users to define extensions simply without needing to understand the underlying system architecture.
Solution Approach 2:
The extension mechanism is designed to be universal, working across all business objects through a common metadata framework. The same propagation logic applies to different field types and business objects, reducing the need for specialized handling of each case and simplifying the overall system.
3Adaptability or versatility
If extension fields are propagated to multiple business objects, then functionality is enhanced, but data flow management complexity increases
Solution Approach 1:
The system segments data flow management by associating extension fields with specific data flows rather than managing all propagations globally. Each data flow is independently configured with its own propagation rules, allowing fine-grained control and simplifying the management of complex multi-object extensions.
Data Source
AI summary
A system and method for creating extension fields for business objects are described. In various embodiments, a system includes modules to display business processes and business objects thereof in graphical user interface screens. In various embodiments, the system propagates created extension fields to other business objects via metadata derived from selections in the graphical user interface. In various embodiments, a method for propagating extension fields from one business object to another business object via a data flow between the two business objects is presented. In various embodiments, the method receives instructions from a graphical user interface for the propagation of an extension field and sends instructions to a backend module to propagate the extension field from the source business object to the other business object.