Context-Aware Workflow Engine Decouples Logic From Definitions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current workflow technologies require extensive redevelopment and testing for every change in workflow definitions or business conditions, leading to a heavy workload due to tight coupling between workflow applications and definitions, and the inability to create generic applications adaptable to various user roles, stages, functions, and work item types.
Innovation Solution
A method and apparatus for generating context-aware generic workflow applications by developing generic workflow functional modules, deploying them to workflow nodes, creating context-aware configuration data, and executing context-aware logics based on the current workflow context to adapt to different situations dynamically.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If workflow applications are tightly coupled with workflow definitions, then workflow execution reliability is improved, but adaptability to business changes deteriorates
Solution Approach 1:
The patent segments the workflow application into two independent parts: workflow definitions (describing process flow, nodes, and transitions) and workflow applications (containing business logic and data processing). This decoupling allows each part to be modified independently, improving adaptability while maintaining execution reliability through the preserved interface contract between components.
Solution Approach 2:
The patent creates a universal workflow engine that can execute multiple different workflow definitions and application types through a standardized interface. This multi-functional engine handles various business scenarios without requiring dedicated custom code for each workflow, thereby improving adaptability to business changes while maintaining reliable execution through consistent engine logic.
2Adaptability or versatility
If custom workflow applications are developed for each workflow definition, then functional requirements are met, but development workload increases
Solution Approach 1:
The patent implements a universal workflow application framework that serves multiple workflow definitions through parameterization and configuration rather than custom development. The same application code can handle different workflows by receiving context parameters and configuration data, dramatically reducing development workload while still meeting specific functional requirements through flexible configuration.
Solution Approach 2:
The patent uses parameter changes to adapt a single workflow application to multiple workflow definitions. By passing different context parameters (workflow ID, node ID, task type, data models) to the same application framework, the system meets diverse functional requirements without requiring separate application development for each workflow scenario.
3Adaptability or versatility
If workflow applications are redeveloped whenever workflow definitions change, then workflow definition updates are supported, but testing workload increases
Solution Approach 1:
The patent segments workflow definitions from workflow applications, allowing workflow definitions to be updated independently without triggering application redevelopment. The workflow engine reinterprets new definitions using the same application framework, significantly reducing testing workload since application logic remains unchanged and only configuration or parameter mappings need verification.
4Adaptability or versatility
If separate workflow applications are created for different user roles and stages, then user-specific requirements are met, but system complexity increases
Solution Approach 1:
The patent applies local quality by injecting user-specific context (role, stage, permissions) into a generic workflow application at runtime. Instead of creating separate applications for each user role, the system modifies the behavior of a single application locally based on the current execution context, meeting user-specific requirements while avoiding the complexity of multiple application versions.
Solution Approach 2:
The patent creates a universal workflow application that serves multiple user roles and workflow stages through context-aware parameterization. The same application code adapts its behavior based on context parameters indicating user role, workflow stage, and task type, thereby fulfilling user-specific requirements without increasing system complexity through code duplication.
Data Source
AI summary
A method and apparatus for generating context-aware generic workflow applications is provided. The apparatus comprises: one or more generic workflow functional modules deployed on one or more workflow nodes of a workflow; a context-aware configuration storage device configured to store context-aware configuration data including context-aware logics; a context obtaining module configured, in response to the execution of the workflow on a workflow node, to obtain the current context of the workflow execution; a context-aware logic management module configured to retrieve context-aware logics matching the current context in the context-aware configuration data stored in the context-aware configuration storage device; wherein a relevant workflow functional module in the one or more generic workflow functional modules is configured to execute relevant operations according to the matched context-aware logics, thus generating a context-aware generic workflow application. The apparatus and method of the invention can generate generic workflow applications applicable to various workflows and contexts, which saves the developing and testing costs of workflow applications.