Normal Change Flow Migration – Prevent On Hold Logic from Affecting Previous Approval Stages
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
I am currently migrating a Normal Change Workflow to Flow Designer and am facing an issue with handling approvals when the Change is placed On Hold.
Current behavior:
In the Assess state, Peer Approval is requested.
If the Change is moved to On Hold, the Peer Approval records are updated to No Longer Required.
When On Hold is removed, those Peer Approval records are reverted back to Requested.
Once Peer Approval is approved, the Change moves to the Authorize state.
In the Authorize state, CAB Approval is requested.
Similar to Peer Approval, if the Change is moved to On Hold, the CAB Approval records are updated to No Longer Required, and when On Hold is removed, they are reverted back to Requested.
To achieve this, I am using a Do the Following Until State = Authorize loop in the Assess phase.
The issue I am facing is that when the flow enters the Authorize phase and CAB Approvals are generated, the On Hold logic is also affecting the previous Peer Approval records. Those Peer Approvers are being changed back and forth between Requested and No Longer Required, even though they have already completed their approval in the Assess state.
My requirement is:
Once Peer Approval is completed and the Change moves to Authorize, the previous Peer Approval records should no longer be affected by the On Hold logic.
When CAB Approval is active, the On Hold processing should only affect the current CAB Approval records and not any approvals that were generated in the Assess phase.
What would be the best approach in Flow Designer to ensure that On Hold handling only impacts the currently active approval stage and does not update approval records from previous stages?
