Container Application Parameter Conversion for Cross-App Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Different computer applications often use incompatible parameters to generate and display data, making it difficult to link between them and share relevant information, especially when one application is based on SAP's Object Based Navigation (OBN) and the other is not, leading to issues in data retrieval.
Innovation Solution
A container application intercepts data requests and converts parameters from one application to a format readable by another, allowing seamless linking and data sharing between applications with different parameter types and languages, without requiring changes to the legacy applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a link is created from a page of one application to a page of another application, then data sharing between applications is enabled, but the second application cannot recognize the parameters passed from the first application if they use different parameter types
Solution Approach 1:
The patent introduces a container application as an intermediary component that receives data requests from the first application, converts the parameters from the first application's parameter type to the second application's parameter type, and forwards the converted request to the second application. This mediator resolves the incompatibility between different parameter systems without requiring changes to the legacy applications.
Solution Approach 2:
The container application dynamically changes parameters from one type to another based on the target application's requirements. It translates parameters between different parameter languages and types (e.g., OBN-based parameters to non-OBN parameters) while preserving the semantic meaning and session context, enabling seamless integration between applications with different parameter systems.
2Adaptability or versatility
If parameters are converted between different application formats, then integration between applications is enabled, but additional conversion logic and a container application are required
Solution Approach 1:
The container application is designed as a universal integration layer that can handle parameter conversion between multiple different application types and parameter systems. It provides multi-functional capability to work with various OBN-based and non-OBN-based applications, reducing the need for application-specific integration code and simplifying the overall system architecture.
3Ease of manufacture
If legacy applications are left unchanged, then development time is reduced, but they cannot directly communicate with applications using different parameter systems
Solution Approach 1:
The container application serves as an intermediary that allows legacy applications to maintain their original parameter systems while still enabling communication with modern applications. The translation layer handles all parameter conversion, allowing legacy systems to remain unchanged and continue functioning as intended while gaining integration capabilities.
Data Source
AI summary
In a system and method for linking between data output by a plurality of applications, in response to a first data request addressed to a first application, the first request generated upon selection of a link in a page generated by a second application and displayed at a terminal, the first request including a first parameter, a processor may select a second parameter that is readable by the first application and that is equivalent to the first parameter, may transmit to the first application a second request for the data, the second request including the second parameter, and may transmit the data to the terminal after the data is output by the first application.