Rules Engine Integrating Multiple Applications for Transaction Efficiency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In the financial and sales industries, users face inefficiencies in business transactions due to the complexity of navigating multiple incompatible applications, leading to customer dissatisfaction and decreased productivity, as existing methods fail to automatically communicate and integrate information across applications based on transaction types, requiring manual data retrieval and input.
Innovation Solution
A method and apparatus that utilize a rules engine, application integrator, and integrated user interface to communicate with multiple applications based on end user, client, and transaction type information, automatically integrating and presenting relevant data in a single interface, thereby streamlining transactions and enhancing user interaction.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple incompatible applications are used to support various transactions, then the functionality and versatility of the system is improved, but the complexity of navigation and operation deteriorates
Solution Approach 1:
The system segments the multiple applications into distinct functional modules that can be independently managed and accessed. Each application maintains its own functionality while being organized under a unified navigation structure, allowing users to access specific applications based on transaction needs without being overwhelmed by the entire system complexity.
Solution Approach 2:
A universal interface layer is implemented that provides consistent access methods across all applications. This interface serves multiple functions: it acts as a navigation hub, provides unified authentication, and enables standardized interaction patterns regardless of which underlying application is being accessed, thereby improving ease of operation while maintaining versatility.
2Adaptability or versatility
If multiple incompatible applications are integrated into a desktop system, then the range of supported transactions is improved, but the device complexity increases
Solution Approach 1:
An intermediary integration layer is introduced between the user interface and the multiple applications. This mediator handles application compatibility issues, manages data exchange protocols, and coordinates communication between different applications, thereby reducing the apparent system complexity for users while maintaining broad transaction support capability.
Solution Approach 2:
The system employs a nested architecture where a master control application contains or orchestrates multiple subordinate applications. Each subordinate application is nested within the overall system structure, allowing them to be managed as part of a unified whole while maintaining their individual functionality, thus supporting diverse transactions without proportionally increasing perceived complexity.
3Reliability
If manual data retrieval and input between applications is required, then application independence is maintained, but productivity and transaction speed deteriorate
Solution Approach 1:
The intermediary layer automatically retrieves data from one application and inputs it to another application based on transaction requirements. This automated data flow maintains application independence by not requiring direct integration between applications, while simultaneously improving productivity by eliminating manual data transfer operations.
Solution Approach 2:
The system implements feedback mechanisms where the intermediary layer monitors transaction progress and automatically triggers data retrieval and input operations between applications. This feedback-driven automation ensures that data flows efficiently between applications without manual intervention, maintaining both application independence and high transaction speed.
Data Source
AI summary
A method and apparatus provides information to enhance at least one of: a sales, a service and an administrative transaction by communicating with a plurality of applications from a group of applications in accordance with rule information and based on at least two of the received: end user identification information, client identification information and transaction type information. In one example, the apparatus includes a rules engine, an application integrator, an integration and presentation module, and an integrated user interface. The rules engine causes the application integrator to communicate with a plurality of applications in accordance with the rule information, and at least two of: the end user identification information, the client identification information, and the transaction type information. The application integrator then generates integrated output information received from the plurality of applications to produce the integrated user interface that includes output from the plurality of applications. Based on end user input, the integrated user interface then provides interactive user response information to the application integrator which passes the interactive user response information to the rules engine. The rules engine then determines which of at least one additional supporting application of available applications to use in a next stage of the transaction, which may be the same as or different applications from the plurality of applications. The application integrator then communicates with the additional supporting applications and accordingly updates the integrated output information on the integrated user interface to include output from the at least one additional supporting application.