Logical Business Object Broker for Dynamic Data Binding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems lack a mechanism for non-technical users to access and manage information from multiple data sources as logical business objects, requiring technical skills for customization and integration, and do not provide tools for both technical and non-technical users to author business processes seamlessly.
Innovation Solution
The system employs an Enterprise Application Integration (EAI) framework with a runtime broker and adapter services, allowing users to define logical business objects and actions from various data sources, enabling dynamic binding and personalization without technical involvement, and facilitates process automation through a unified modeling environment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If existing EAI systems with development tools are used to custom develop solutions, then data accessibility is improved, but device complexity and difficulty of operation increase due to hard-coded solutions requiring significant technical and development skill to maintain and change
Solution Approach 1:
The system implements dynamic form binding where data sources, fields, and business objects can be configured and modified at runtime without recompilation. The form binding information is stored in a data store and can be dynamically loaded, allowing non-technical users to change data accessibility configurations through a user interface without involving technical personnel.
Solution Approach 2:
The patent introduces a form binding mechanism that acts as an intermediary layer between the user interface and data sources. This binding information serves as a configurable mediator that can be modified through user-friendly interfaces, eliminating the need for direct technical intervention while maintaining data accessibility.
2Loss of information
If existing EAI systems are used to integrate data between systems, then information integration is improved, but device complexity increases as no workable mechanism exists for non technical users to add information within a logical business object definition without involving technical or development skills
Solution Approach 1:
The system enables non-technical users to independently configure and customize business objects through a user interface. Users can add, modify, and remove fields and data source bindings without requiring technical assistance. The system automatically handles the complexity of integration through the form binding mechanism, allowing users to self-service their information integration needs.
Solution Approach 2:
The form binding mechanism serves multiple functions: it integrates data from multiple sources, allows user customization, stores configuration information, and provides a unified interface for both technical and non-technical users. This universal mechanism handles various integration scenarios through a single configurable system.
3Ease of operation
If existing form technologies are used, then basic form functionality is provided, but ease of operation deteriorates as the information worker's ability to add additional information on-demand to existing forms based on its current state and context is extremely limited
Solution Approach 1:
The system implements dynamic form binding where additional information sources can be bound to existing forms at runtime based on user needs and context. The form configuration is not fixed but can be dynamically extended by binding additional data sources and fields without requiring application recompilation or technical intervention.
Solution Approach 2:
The system pre-establishes a form binding framework that allows users to later add information sources as needed. The infrastructure is prepared in advance to support dynamic binding, enabling users to quickly add information without complex setup procedures when business needs arise.
4Adaptability or versatility
If custom developed solutions are created to provide additional functionality, then adaptability is improved, but device complexity and loss of time increase due to dependence on application specific pre-developed functionality and technical involvement
Solution Approach 1:
The system allows users to create and configure additional functionality through a user interface without requiring custom development. Users can bind additional data sources, add fields, and customize forms independently, eliminating the need to wait for technical personnel to implement requested features and significantly reducing the time to add functionality.
Solution Approach 2:
The form binding mechanism provides a universal platform that handles various customization scenarios without requiring separate custom developments. Whether binding to existing data sources or adding new information, the same mechanism is used, providing consistent adaptability across different functionality requirements.
Data Source
AI summary
The disclosed system empowers technical and non technical users to author logical business objects, author intelligent business forms, and create automated workflows. The logical business objects include data definitions and methods from existing and new data sources. An object broker interprets the business object definition and brokers data/information and method calls to the data sources. The intelligent business forms are created by an information worker in a rich web-based tooling environment. Each form is intelligent enough to recognize other forms that it might co-exist with on a single page, as well as how to react based on events that occur on these related forms. The automated workflow tools include process discovery features that assist users during the process identification phase. The tools assist both technical and non technical users to identify processes within the organization, including supporting solution artifacts such as forms, rules, actions, outcomes and business objects involved. Process modeling features include the ability to combine defined artifacts into a process model that can be published into a runtime environment where it can be executed and used by business users in the organization.