Workflow Management System with Segmented Queues
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing information processing technologies lack diversification in workflow driving manners and concurrent control systems, leading to interference between different workflow types, which limits their ability to meet diverse user requirements and scheduling scenarios.
Innovation Solution
The solution involves configuring separate dispatchers, waiting queues, event handlers, and submitters for different workflow types, such as manual, timed, re-scheduling, and parameter-driven workflows, allowing each type to have distinct processing logic and concurrent control systems, enabling flexible and diversified scheduling.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a shared queue and concurrent control system are used for all workflow types, then system complexity is reduced, but different workflow types interfere with each other and cannot execute concurrently
Solution Approach 1:
The patent divides the unified workflow system into multiple independent workflow types (manual workflow, timed workflow, triggered workflow, etc.), each with its own queue and concurrent control system. This segmentation allows different workflow types to execute independently without interfering with each other, while maintaining overall system manageability through modular architecture.
2Device complexity
If only two types of workflows (manual and timed) are supported, then system complexity is low, but diverse user requirements cannot be met
Solution Approach 1:
The patent creates a universal workflow management system that can handle multiple workflow types (manual, timed, triggered, scheduled, etc.) through a common framework. Each workflow type implements the same core interface but with different execution logic, allowing the system to be both simple to operate and highly adaptable to diverse user needs.
3Device complexity
If the same processing logic is used for all workflow types, then system complexity is reduced, but different timeliness requirements of different workflows cannot be satisfied
Solution Approach 1:
The patent applies different processing logic and execution strategies to different workflow types based on their specific requirements. For example, manual workflows use immediate execution logic, timed workflows use scheduled execution logic, and triggered workflows use event-driven execution logic. This local customization of processing logic ensures each workflow type meets its timeliness requirements without complicating the overall system.
Data Source
AI summary
The present disclosure provides technical solutions for managing different types of workflow, including preconfiguring a dispatcher, a waiting queue, an event handler, a delivery queue, and a submitter for each type of workflow; receiving a workflow request including workflow information based on user's activities; determining a type of the received workflow request; in accordance with a determination that the received workflow request is not a type of manual workflow request: generating key information including one or more parameters; writing the key information into a first waiting queue using a first dispatcher; reading the key information from the first waiting queue in sequence using a first event handler; generating a workflow instance based on the key information; writing the workflow instance into a first delivery queue; reading the workflow instance from the first delivery queue using a first submitter; and sending the workflow instance to a corresponding execution node to execute the workflow instance.