State Transition Rule Versioning for In-Process Workflow Changes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for managing state transitions in product distribution do not allow for version changes during the transition process, making it impossible to add or delete states based on version requirements.
Innovation Solution
A state transition management apparatus that includes a reception unit for receiving state transition rules and a rule registration unit to set initial version numbers for each transition, enabling version changes during the transition process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If state transition rules are managed without version control, then the system is simpler to operate, but version changes cannot be made during state transitions
Solution Approach 1:
The system performs preliminary action by establishing version control mechanisms and initial version numbers before state transitions occur. The rule registration unit sets initial version numbers for each state transition in advance, enabling subsequent version changes during transitions without disrupting the overall system structure.
Solution Approach 2:
The system applies dynamics by making version numbers changeable and adjustable during state transitions. Instead of fixed version control, the system allows dynamic version changes through the reception unit and rule registration unit, enabling the version to be modified based on real-time requirements while maintaining rule compliance.
2Reliability
If version numbers are not set for state transitions, then the registration process is faster, but compliance verification becomes difficult
Solution Approach 1:
The system performs preliminary action by pre-establishing version numbers and rules before state transitions. The rule registration unit sets initial version numbers in advance, so that when state transitions occur, the version information is already in place for immediate compliance verification without delaying the registration process.
Solution Approach 2:
The system applies feedback by implementing compliance verification that provides immediate feedback on whether state transitions adhere to the predefined rules and version numbers. The state verification unit checks compliance and provides feedback, ensuring reliability while maintaining efficient registration through automated verification.
3Adaptability or versatility
If state transitions cannot be restarted from the beginning, then the workflow is more efficient, but flexibility to correct errors is reduced
Solution Approach 1:
The system applies dynamics by making the state transition path flexible and adjustable. Through version control and the ability to change versions during transitions, the system allows corrective actions and restarts from specific version points without requiring a complete workflow restart, balancing flexibility with efficiency.
Solution Approach 2:
The system applies segmentation by dividing the state transition workflow into manageable segments based on version numbers. Instead of treating the entire workflow as a single unbreakable process, the system segments it into version-based stages, allowing selective restarts and corrections at specific version points while maintaining overall workflow efficiency.
Data Source
AI summary
When a received state transition rule is a rule for registration, a rule registration unit (112) sets an initial version number for each of state transitions in the rule for registration, as an event, and registers the set rule for registration to a rule storage unit. When a received state transition rule is a rule for updating, the rule registration unit (112) selects from the rule storage unit, a state transition rule whose type is the same as that of the rule for updating, adds to the selected state transition rule, each of state transitions that are not present in the selected state transition rule, among the state transitions in the rule for updating, and sets for each of the state transitions in the selected state transition rule, the version number next to the latest version number in the selected state transition rule, as an event.