Metadata-Driven Workflow Task UI Generation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The traditional development and deployment of user interfaces (UIs) for cloud-based applications, particularly those interacting with OData services, are time- and resource-intensive, requiring skilled developers and lengthy development cycles, hindering the progress of developing and deploying cloud-based applications.
Innovation Solution
A no-code, metadata-driven approach to generate workflow task UIs, allowing users to interact with cloud-based applications without manual coding, using a design-time environment that receives user input for decision elements and data objects, and provides executable files with metadata logic to update workflow backends, enabling efficient development and deployment of workflow task UIs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If traditional development and deployment of user interfaces for cloud-based applications is used, then the UIs can be fully customized and integrated with OData services, but the process is time- and resource-intensive, requiring skilled developers and lengthy development cycles
Solution Approach 1:
The patent introduces a metadata-driven intermediary layer that sits between the traditional development process and the final UI deployment. This metadata layer contains pre-defined templates, data models, and integration patterns that automatically generate UI code and configure OData service connections, eliminating the need for manual coding while maintaining full customization capabilities
Solution Approach 2:
The system performs preliminary actions by pre-configuring metadata templates, data models, and integration patterns before actual UI development is needed. These pre-prepared artifacts contain common UI patterns, data bindings, and service integrations that can be rapidly instantiated and customized, dramatically reducing development cycle time while maintaining full functionality
2Productivity
If traditional development approaches are used, then comprehensive control over UI behavior and integration can be achieved, but skilled developers are required and resource consumption increases
Solution Approach 1:
The metadata-driven system enables self-service UI development where business users can configure and deploy UIs without requiring skilled developers. The metadata templates and automated code generation handle the complexity of OData service integration, data modeling, and UI programming automatically, allowing users with basic knowledge to create production-ready interfaces
Solution Approach 2:
The system changes the fundamental parameters of UI development by shifting from code-based configuration to metadata-based configuration. This parameter change transforms the development process from requiring programming expertise to using declarative metadata definitions, thereby reducing the complexity barrier while maintaining comprehensive control over UI behavior and integration
Data Source
AI summary
Methods, systems, and computer-readable storage media for receiving user input representative of user selection of a set of decision elements to be included in a workflow task UI and a data object, each decision element being associated with a decision identifier, the workflow task UI including a container component and metadata, the container component storing parameters of the application at run-time, the metadata including logic that is executable within a view of the container component during run-time, during run-time use of the application: displaying the workflow task UI, and receiving user input to a decision element within the view of the container component, and in response, passing a decision identifier associated with the decision element from the container component to the metadata, and executing at least a portion of the logic of the metadata to update the decision identifier with a workflow backend to complete the task.