Extension Fields for Business Mashup Customization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Business service providers face limitations in customizing mashups for clients due to preset bindings, which restrict the use of custom fields not available in base classes, limiting the types of data that can be bound and integrated from external services into business applications.
Innovation Solution
The introduction of extension fields allows users to create custom fields that can be bound to mashup components, enabling the integration of additional data types, such as social network IDs, by defining these fields within the business application and configuring bindings through user interfaces, thereby expanding the data that can be used in mashups.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If preset bindings are used in business applications, then integration with external services is enabled, but customizability is limited
Solution Approach 1:
The binding mechanism is segmented into two distinct types: preset bindings for standard integration scenarios and custom bindings for specialized needs. This segmentation allows users to choose the appropriate binding type based on their requirements, enabling customizability while maintaining system simplicity through clear separation of concerns.
Solution Approach 2:
The binding system transitions from a static, provider-defined configuration to a dynamic system where clients can create and modify custom bindings in real-time. This dynamic capability allows the system to adapt to changing requirements without requiring service provider updates, resolving the contradiction between adaptability and complexity.
2Ease of operation
If service provider defines all bindings, then system management is simplified, but client autonomy is reduced
Solution Approach 1:
The system empowers clients to perform self-service by enabling them to create custom bindings independently without requiring service provider intervention. Clients can define their own binding relationships between business data and mashup components, eliminating update dependency and granting full autonomy over their data integration needs.
3Adaptability or versatility
If only base class fields are bound, then data integration is straightforward, but data type coverage is limited
Solution Approach 1:
The binding mechanism is designed to be universal, supporting both base class fields and custom extension fields through a unified interface. This multi-functionality allows the same binding infrastructure to handle standard data types and specialized custom fields, expanding data type coverage without proportionally increasing configuration complexity.
Data Source
AI summary
A method for value-added usage of process-oriented extension fields in business mashups may include generating, using at least one processor, a mashup component with an unbound parameter; receiving input identifying the creation of an extension field, the extension field tied to data stored in a database; binding the unbound parameter of the mashup component to the extension field; presenting an application interface, the application interface including the extension field; receiving a request to load the mashup component; and in response to receiving the request, passing the data tied to the extension field as an input parameter to the mashup component.