Dynamic Region Segmentation for Real-Time GRC Page Composition
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional software applications, particularly GRC applications, lack flexibility for customization, requiring expertise that often leads to additional costs and downtime for updates, as they are designed for general use and lack adaptability to specific business processes and regulatory compliance needs.
Innovation Solution
A method and system utilizing task flows for real-time page and flow compositions, allowing non-technical users to customize application pages through a modular approach with dynamic regions, metadata generation, and a library of page templates and user interface components, enabling business users to construct and modify pages without needing an IDE tool.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If application pages are hard coded at design time with static components, then the application structure is stable and easy to maintain, but the application lacks flexibility for changes and requires downtime for updates
Solution Approach 1:
The application page is segmented into static components and dynamic regions. Static components remain hard-coded for stability, while dynamic regions are separated out to accommodate runtime task flows. This segmentation allows the page to maintain structural integrity while gaining flexibility through可替换的动态内容.
Solution Approach 2:
The invention introduces dynamic regions that can be configured at runtime rather than design time. These dynamic regions allow task flows to be modified, added, or removed without requiring application downtime, transforming the static page structure into a dynamic, adaptable system.
2Adaptability or versatility
If a software engineer is employed to customize the application for a specific use, then the application can be effectively modified, but additional expense is incurred and the engineer may lack familiarity with business processes
Solution Approach 1:
The system enables business users to perform customization themselves through a simplified interface that presents task flows as business processes rather than technical code. Users can drag and drop task flows into dynamic regions without needing programming knowledge, making the system self-sufficient for customization needs.
Solution Approach 2:
The invention introduces an intermediary layer between the user and the application code. This layer presents a simplified, business-oriented interface that translates user actions into technical configurations, allowing business users to customize applications without directly manipulating code.
3Adaptability or versatility
If the application is taken off-line to update the page design, then the design can be modified, but downtime causes loss in productivity and additional expense
Solution Approach 1:
The invention enables dynamic configuration of task flows at runtime without requiring the application to be taken offline. Business users can modify, add, or remove task flows in dynamic regions while the application remains operational, eliminating downtime and associated productivity losses.
Solution Approach 2:
The system performs preliminary configuration work by separating dynamic regions from static components at design time. This preliminary action prepares the infrastructure for runtime modifications, allowing changes to be made without downtime because the architectural framework is already in place to support hot-swapping of task flows.
4Productivity
If conventional GRC applications are designed for general use, then they can be distributed to many customers, but they lack effectiveness for specific organizational needs and constant changes
Solution Approach 1:
The GRC application is segmented into standardized core functionality and customizable task flow components. The core GRC functions remain consistent for efficient deployment, while task flows in dynamic regions can be customized to match specific organizational policies and regulatory requirements, enabling both rapid deployment and local adaptation.
Solution Approach 2:
The invention creates a universal framework that can serve multiple organizations with different needs. The standardized GRC application provides a common foundation that works across diverse organizations, while the dynamic task flow regions allow each organization to configure the system for their specific requirements, making the application universally applicable yet locally adaptable.
Data Source
AI summary
Task flows are utilized for real-time page compositions, real-time flow compositions, or both. At design time, a plurality of task flows are provided as a database or library. A manager, or other type of user, can associate task flows with dynamic regions in an application page being designed. The application page can include one or more dynamic regions that act as a container for task flows. Metadata is generated from the customization of input parameters. At runtime, application pages are generated on-the-fly for display in a user interface. The application pages are composed according to the task flows embedded therein. The application pages are presented to the user according to an application flow. Through a user interface, the user can enter and retrieve information related to governance, risk, and compliance (GRC) activities, or other types of activities.