Dynamic Workflow Orchestration via Policy File Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing business process execution language (BPEL) workflows are static and require changes when new processes are added, limiting the ability to dynamically invoke web services based on user attributes, which restricts flexibility and efficiency in orchestrating business processes.
Innovation Solution
A method and system that utilize a policy file to associate attributes with processes, allowing user input to select the appropriate process and invoke web services dynamically, enabling reconfiguration of workflows by modifying the policy file and grouping processes into categories for flexible execution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If BPEL workflows are designed with static processes for all possibilities, then the workflow can be executed with defined logic, but the ability to dynamically adapt to new processes or user attributes is limited
Solution Approach 1:
The patent applies dynamics by transitioning from static BPEL workflows to dynamic workflows where the process execution path is determined at runtime based on user attributes. The system dynamically selects which child processes to execute based on the user's role, department, or other attributes, allowing the workflow to adapt its structure during execution rather than being fixed in advance.
Solution Approach 2:
The patent segments the workflow into parent processes and selectable child processes. Instead of defining all possible processes statically, the system segments the workflow into a framework (parent processes) and configurable components (child processes), where the selection of child processes is determined dynamically based on user attributes, reducing overall complexity while maintaining adaptability.
2Reliability
If BPEL workflows are designed to handle all possibilities with defined logic, then the workflow execution is reliable, but changes are required when new processes are added
Solution Approach 1:
The system maintains reliability by executing workflows through defined parent processes while enabling ease of process addition through dynamic child process selection. New child processes can be added to the policy file without modifying the BPEL logic, allowing the system to adapt to new business needs while maintaining execution reliability through the structured parent process framework.
Solution Approach 2:
The patent introduces a policy file as an intermediary between the BPEL workflow logic and the actual process execution. The policy file acts as a mediator that maps user attributes to child processes, allowing changes in business requirements to be implemented by modifying the policy file rather than changing the core BPEL logic, thus maintaining reliability while enabling easy adaptation.
3Ease of operation
If workflows are manually configured for each scenario, then the workflow can be precisely controlled, but the time and effort required for configuration increases
Solution Approach 1:
The system implements self-service by automatically determining which child processes to execute based on user attributes. Instead of manually configuring workflows for each scenario, the system automatically selects and executes the appropriate child processes based on the user's role, department, or other attributes, significantly reducing configuration time and effort while maintaining precise control.
Solution Approach 2:
The patent applies preliminary action by pre-defining the mapping between user attributes and child processes in the policy file. This preliminary configuration allows the system to automatically determine the execution path without manual intervention during actual workflow execution, reducing the time and effort required for configuration while maintaining precise control over the workflow.
Data Source
AI summary
Techniques for orchestrating workflows are disclosed herein. In an embodiment, a method of orchestrating a workflow is disclosed. In an embodiment, data is stored in a policy file which associates attributes with processes. User input is received. A process associated with an attribute is selected, where the attribute is based on the user input. The selected process is performed as part of the workflow. Also, processes may be added dynamically as part of any category inside the policy file without having to recompile or redesign the logic of the BPEL project.