Workflow overhaul #1146
jekabs-karklins
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Upcoming Workflow Engine Changes
We’re implementing four key improvements to make workflows more robust, flexible, and easier to maintain. Feedback is welcome.
Event Validity
Events must now occur while the proposal is in the source state to trigger a transition.
Prevents outdated events (e.g., PROPOSAL_UPDATED before entering state A) from causing unintended moves.
Conditions
Transitions can now require state-based conditions in addition to events.
Example: Event PROPOSAL_INSTRUMENT_ADDED + Condition PROPOSAL_HAS_INSTRUMENT = true.
Allows finer control and avoids unnecessary transitions.
Circular Workflows
We can now safely return to earlier states without infinite loops, thanks to event validity + conditions.
Supports iterative review cycles without hacky detours.
Multiple States per Status ID
Different workflow states can share the same statusId but have unique exit rules.
Example: Two REJECTED states with different recovery paths.
Enables richer branching and context-specific transitions.
Comments welcome, especially on backward-compatibility and circular workflow safeguards.
Beta Was this translation helpful? Give feedback.
All reactions