No-Code Workflow Task Provisioning for Cloud Platforms
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current workflow management systems require professional developers with extensive technical knowledge to provision and develop workflow task applications, limiting their reusability across multiple projects and increasing development time and resource consumption.
Innovation Solution
Implementing a no-code approach that decouples workflow components from workflow-specific properties, enabling citizen developers to create and reuse metadata-driven workflow tasks through automatic integration with service tasks and data services, without the need for coding, using tools like Workflow MyInbox and Core Data Services.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If professional developers with extensive technical knowledge are used to provision workflow task applications, then the reliability and functionality of the workflow system is improved, but the development time and resource consumption increase significantly
Solution Approach 1:
The patent enables citizen developers (non-technical users) to self-provision workflow task applications using a no-code interface. The system provides pre-configured templates and automated generation of workflow components, allowing users to create applications independently without requiring professional developers, thus reducing development time while maintaining functionality through standardized patterns.
Solution Approach 2:
The patent implements pre-configured workflow templates and pre-built application patterns that can be reused across multiple projects. By preparing these templates in advance with common workflow patterns already defined, the system eliminates the need for developers to build from scratch, significantly reducing development time while ensuring reliable, tested functionality.
2Reliability
If workflow components are tightly coupled with workflow-specific properties, then the functionality for specific workflows is improved, but the reusability of components across multiple projects decreases
Solution Approach 1:
The patent segments workflow applications into reusable components (tasks, decisions, actions) that can be independently configured and assembled. Each component is designed as a modular unit with standardized interfaces, allowing them to be reused across different workflows and projects while maintaining their specific functionality through configuration rather than hard-coded coupling.
Solution Approach 2:
The patent creates universal workflow components that can serve multiple functions across different projects. By designing components with configurable parameters and standardized interfaces, a single component template can be adapted to work in various workflow contexts, increasing reusability while maintaining workflow-specific functionality through configuration rather than customization.
3Adaptability or versatility
If custom-coded workflow applications are developed for each project, then the specific requirements of each project are met, but the development resources and complexity increase
Solution Approach 1:
The patent enables copying and reusing of workflow templates, components, and patterns across multiple projects. Instead of coding each application from scratch, users can replicate proven templates and customize them for specific project requirements, significantly reducing development complexity while maintaining the ability to meet project-specific needs through configuration.
Solution Approach 2:
The patent implements dynamic configuration capabilities where workflow components can be easily adjusted and adapted to different project requirements without requiring code changes. The system allows users to dynamically modify parameters, add or remove components, and reconfigure workflows through a user interface, reducing development complexity while maintaining adaptability to specific project needs.
Data Source
AI summary
Methods, systems, and computer-readable storage media for receiving data as input to a workflow task user interface (UI) provided by a workflow task application, the data being representative of a task of a workflow, and determining that a decision action has been executed in response to user input to a UI element representative of the decision action, and in response, providing, from the workflow task application through an entry application within which the workflow task application executes, an update entity request, inserting, by the entry application, a set of properties to a header of the update entity request, and transmitting the update entity request to a data service to update a data object at least partially based on the data, a workflow service updating an instance of the workflow based on the set of properties.