Business Process Extension via State Machine Mediator
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing business process management systems lack flexibility to accommodate user-specific processes without causing complications during system upgrades or integrations, as they require modifications that may lead to incompatibilities with new systems or overwrite existing modifications.
Innovation Solution
Implementing a state machine with loose coupling between program components using a database to manage status updates, allowing for asynchronous execution and optional extensions to the computational tasks without reconfiguring the core system, enabling user-specific process modifications and distributed data processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If user-specific process modifications are implemented in existing business process management systems, then the systems can accommodate custom workflows, but complications arise during system upgrades or integrations due to incompatibilities and overwriting of modifications
Solution Approach 1:
The patent introduces an intermediary layer (extension mechanism) between the core system and user-specific modifications. This intermediary allows custom processes to be added without directly modifying the core system, thus preserving upgrade compatibility while enabling adaptability.
Solution Approach 2:
The system is segmented into a core component and an extension component. The core system remains unchanged and upgradeable, while user-specific modifications are implemented as separate extensions that can be added or removed without affecting the core system's stability and compatibility.
2Stability of the object's composition
If program components are tightly coupled to ensure sequential processing, then workflow order is preserved, but flexibility to add or modify computational tasks without reconfiguring the core system is reduced
Solution Approach 1:
A state machine acts as an intermediary that manages the sequential processing of workflow tasks while allowing flexible addition of extension tasks. The state machine monitors status changes and triggers appropriate tasks without requiring tight coupling between all program components, thus maintaining workflow integrity while enabling extension flexibility.
Solution Approach 2:
The system uses dynamic task registration and execution based on status changes. Instead of static, fixed sequencing, the system dynamically determines which tasks to execute next based on current state, allowing flexible addition of tasks while preserving sequential processing through the state machine's control logic.
3Adaptability or versatility
If the core system is modified to accommodate user-specific processes, then customization is achieved, but modifications and delay of the core system increase
Solution Approach 1:
The extension mechanism serves as an intermediary that provides customization capability without requiring modifications to the core system. User-specific processes are implemented as separate extension tasks that interact with the core system through defined interfaces, thus achieving adaptability while minimizing core system complexity.
Solution Approach 2:
Instead of modifying the core system directly, the patent creates copies or extensions of the necessary functionality. User-specific processes are implemented as separate task components that replicate or extend core system capabilities without altering the original core system, thus avoiding increased complexity in the core.
Data Source
AI summary
A core system including different program components performing distinct tasks in a workflow sequence that are initiated through status field updates of objects in database may be modified to define a new status triggering additional processes in an action management system. Once the additional processes are completed, the status field may be changed to an original status provided by the core system to trigger a second program component in the workflow sequence. The action management system may contain user customized processes that may be modified and changed independent of the functionality provided by the core system.