Dynamic User Interface Component Aggregation for Multi-Tenant ERP Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Customization of user interfaces in enterprise resource planning (ERP) software architectures is cumbersome and costly, especially for smaller organizations lacking the necessary IT resources and budget, and current solutions fail to efficiently adapt user interfaces based on user permissions and business data, leading to inefficiencies in multi-tenant software delivery architectures.
Innovation Solution
A method that dynamically adapts user interfaces by retrieving and aggregating user interface components based on user identity and authorization, utilizing metadata adaptation mechanisms and service maps to provide tailored functionality, and implements a unified content aggregation mechanism for multi-tenant systems, enabling efficient updates and changes without manual regeneration of content.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If customized user interface features are hard coded for each user class, then user interface functionality is tailored to specific user needs, but customization becomes cumbersome and time consuming
Solution Approach 1:
The system dynamically determines navigation targets and user interface components at runtime based on user identity and authorization class, rather than using static hard-coded configurations. This allows the user interface to adapt to different user classes automatically, eliminating the need for manual customization while maintaining tailored functionality for each user type.
Solution Approach 2:
The system changes the parameters of user interface components based on user authorization classes and identities. By retrieving and aggregating view components according to user-specific parameters (identity, authorization class), the system automatically tailors the user interface without requiring time-consuming manual customization for each user class.
2Productivity
If a centralized database and core software platform are used, then information flows efficiently between business functions, but customization for different organizations and user subsets becomes complex
Solution Approach 1:
The system segments user interface components into separate, retrievable view components that can be independently configured and aggregated. This segmentation allows the core software platform to maintain centralized data management while enabling flexible customization for different organizations and user subsets by selectively assembling components based on user identity and authorization class.
Solution Approach 2:
The system introduces an intermediary layer (the dynamic component retrieval and aggregation mechanism) between the centralized database and the user interface. This intermediary automatically determines which view components to retrieve and aggregate based on user credentials, simplifying customization while maintaining efficient information flow through the centralized platform.
3Adaptability or versatility
If standalone customized software installations are provided, then user interface functionality is tailored to organization-specific business processes, but the expense of customization is high
Solution Approach 1:
The system provides a universal core software platform that can serve multiple organizations and user classes without requiring separate customized installations for each. By using dynamic component retrieval and aggregation based on user identity and authorization class, the system achieves organization-specific customization through a single multi-functional platform, significantly reducing customization expenses while maintaining adaptability to different business processes.
Data Source
AI summary
Upon receiving a request for a user interface view from a user interface, a user identity and a user authorization class for a user of the user interface can be checked against a user registry and an authorization class registry, respectively. A user interface view component can be retrieved according to the user identity and the user authorization class. The user interface view can be generated by aggregating the retrieved user interface view component with at least one other user interface view component consistent with the user identity and user authorization class, and the generated user interface view can be returned for display to the user via the user interface. Related systems, articles of manufacture, and computer-implemented methods are described.