Web-Based Interface Accessing Native ERP Functions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Web-based user interfaces for network server-based computing systems, such as ERP and CRM systems, often limit access to certain services compared to native user interfaces, restricting functionality and user interaction.
Innovation Solution
The system facilitates access to a native user interface via a web-based user interface by launching a native adapter transaction from a web-based transaction, allowing users to execute functions and access services that may not be directly available through the web interface, using a method that involves invoking a native user interface session and executing remote function calls to perform tasks like creating sales orders, thereby integrating web-based and native interfaces for enhanced functionality.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a web-based user interface is used to access server-based computing systems, then accessibility and ease of use are improved, but functionality and service access are limited compared to native user interfaces
Solution Approach 1:
The patent combines the web-based user interface and native user interface into a unified system where both interfaces can coexist and interact. The web interface serves as the primary access point while the native interface is invoked for specific functions, merging the accessibility benefits of web interfaces with the functionality of native interfaces.
Solution Approach 2:
The system introduces an intermediary mechanism that allows the web-based interface to trigger and coordinate with the native user interface. This intermediary enables seamless transitions between the two interface types, allowing users to access full functionality through the web interface while maintaining the operational simplicity of web-based access.
2Adaptability or versatility
If a native user interface is used for each client system, then complete access to all services is provided, but development and deployment complexity increases
Solution Approach 1:
The system implements a universal web-based interface that can serve multiple functions: acting as the primary user interface, serving as a launcher for native interfaces, and providing a unified access point for all services. This eliminates the need to develop and maintain separate native interfaces for different operating systems while still providing complete service access.
Solution Approach 2:
The patent extracts the complex native interface functionality into a separate, on-demand component that is only invoked when specific functions are needed. The web-based interface handles the majority of user interactions, while native interface capabilities are extracted and activated only when required, reducing overall system complexity.
3Ease of manufacture
If a web-based user interface is used, then maintenance and updates are simplified, but access to certain services is restricted or prohibited
Solution Approach 1:
The system implements a dynamic interface architecture where the web-based interface can adapt its capabilities based on user needs and system state. When additional service access is required, the system dynamically invokes the native user interface, allowing the interface to transition from a static web-based model to a hybrid model that provides enhanced functionality when needed.
Solution Approach 2:
The web-based interface is designed with preliminary action capabilities, pre-configuring and pre-loading necessary components and data. When native interface functions are needed, the web interface has already prepared the necessary context and parameters, enabling seamless transitions and reducing the overhead of maintaining multiple interface versions.
Data Source
AI summary
Example systems and methods of Interaction with a native user interface via a web-based user interface are presented. In one example, a web-based transaction identifying a function to be executed in a processing system is launched in a web-based user interface session. A web application is invoked in the web-based transaction. A native user interface session is initiated from the web application. A native adapter transaction based on the web-based transaction is launched in the native user interface session. Execution of the function in the processing system is initiated in the native adapter transaction.