Workflow Version Management for Instance Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current workflow systems only support one version of a workflow, leading to the overwrite or discard of previous versions, requiring significant time and resources to update in-progress instances, and preventing the creation of new instances based on older versions.
Innovation Solution
A system that maintains multiple versions of a workflow, allowing instances to be created and migrated between versions, with conflict resolution mechanisms to ensure seamless transitions, enabling instances to be processed according to their associated version without forced updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a workflow system supports only one version of a workflow, then the system structure is simple, but previous workflow versions are overwritten or discarded, requiring significant time and resources to update in-progress instances
Solution Approach 1:
The patent segments workflow management by maintaining multiple independent workflow versions (v1, v2, v3, etc.) simultaneously in the system. Each version is stored as a separate entity with its own definition and associated instances, allowing the system to handle version diversity without forcing all instances to update uniformly. This segmentation enables parallel coexistence of different workflow versions.
Solution Approach 2:
The patent implements preliminary action by creating and storing multiple workflow versions in advance before they are needed. When a new workflow version is created, it is immediately available in the system alongside previous versions. Instances can be associated with any available version, and version updates are prepared beforehand rather than forcing immediate updates on all running instances.
2Ease of operation
If a workflow system supports only one version of a workflow, then the system is easy to operate, but new instances cannot be created based on older versions
Solution Approach 1:
The patent implements dynamics by making the workflow version association flexible and changeable. Each instance is dynamically linked to a specific workflow version through a version identifier, and this association can be modified as needed. The system allows instances to be created, migrated, or reassigned to different workflow versions based on operational requirements, providing adaptability while maintaining clear version tracking.
3Reliability
If in-progress workflow instances are forced to update to the latest version, then the workflow definition is kept current, but significant time and resources are consumed in the update process
Solution Approach 1:
The patent implements self-service by allowing workflow instances to automatically associate with appropriate workflow versions based on their creation time or explicit version selection. Instances independently maintain their version associations without requiring forced system-wide updates. The system automatically manages version tracking and instance-version matching, eliminating the need for manual or forced update processes.
4Loss of time
If multiple workflow versions are maintained, then instances can remain on previous versions, but the system complexity increases
Solution Approach 1:
The patent implements copying by creating copies of workflow definitions for each version (v1, v2, v3, etc.). Each workflow version is stored as a separate copy with its own unique identifier. Instances are associated with specific version copies rather than a single master definition. This copying approach allows multiple versions to coexist with manageable complexity, as each version is an independent, self-contained entity.
Data Source
AI summary
Techniques are disclosed relating to a system capable of processing instances of different versions of a workflow. The system may store workflow information indicating different versions of a workflow. The system may receive requests to create instances of the workflow. The requests may include a first request associated with a first, non-current version of the workflow and a second request associated with a second, different version of the workflow. The computer system may create a set of instances of the workflow, including a particular instance corresponding to the first request. The computer system may receive a request to migrate the particular instance to a particular version different from the non-current version associated with the first request. The computer system may migrate the particular instance to the particular version of the workflow, such that subsequently received instance data for the migrated particular instance is processed according to the particular version.