Efflux: Process Management: Enable transition chaining (A→B→C without refresh)#765
Open
Efflux: Process Management: Enable transition chaining (A→B→C without refresh)#765
Conversation
Allow process tickets to chain through multiple activities in a single request when all transition conditions are met. Previously, the event handler used a simple "already processed" flag per ticket, blocking all subsequent transition evaluations. This required manual page refreshes to progress through consecutive activities even when conditions were already satisfied. The fix replaces the boolean flag with a visited-activities set, allowing A→B→C chains while still preventing A→B→A loops.
dignin
added
the
2 - clarification
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed change
Enable automatic transition chaining in Process Management.
Currently, when a process ticket transitions from Activity A to Activity B, and the conditions for B→C are already met, the ticket stops at B. The user must reload the page for the next transition to be evaluated.
Root cause: The
TicketProcessTransitionsevent handler uses a simple "already processed" flag per ticket, blocking all subsequent transition evaluations within the same request.Solution: Replace the boolean flag with a visited-activities set. This allows chained transitions (A→B→C) while still preventing actual loops (A→B→A).
Type of change
1 - 🚀 featureAdditional information
Test process: Import the attached Export_PR_Transition_Chaining.yml via Admin → Process Management. Create a process ticket, select any queue, set state to "closed successful", and submit. The ticket should progress directly to "Completed" without page refresh.
Checklist