Cancelling Branch Assignments
- 25 Jun 2024
- 1 Minute to read
- Print
- DarkLight
Cancelling Branch Assignments
- Updated on 25 Jun 2024
- 1 Minute to read
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
Overview
A Merge step can be configured to cancel all other pending branch assignments in a Flow process. The Merge step has the option to factor in certain conditions. For example, if a Split step Branches out to five different Approvals but only requires two, the Merge step will then Cancel the three unworked Tasks that were previously assigned.
Settings
The following example utilizes setting the AllowCancelMerge boolean on the Merge step to cancel an Approval task. The example Forms are arbitrary Approval Forms and could be replaced with a user's specific use case.
On the Properties tab of a Merge step, select AllowCancelMerge. Two Inputs will appear to configure within the Input Properties: Cancel Pending Forms and Cancel Reason.
| Cancel Pending Forms (Boolean) | Cancels all pending Assignments that have not yet been satisfied or completed, if set to true. |
| Cancel Reason (String) | Stored as a comment within a Process Folder if a Process Folder is being utilized. |
There are two options for the Merge Type: This Flow Only and Include Sub-Flows.
| This Flow Only | Applies to merges in the current Flow. |
| Include Sub-Flows | If Sub-Flows are within the Branch, users may need to set this to True. It is important to understand the Scope. For example, there's a flow called Flow A. Flow A contains sub-flow B, and Flow B contains sub-flow C. If a user uses the Include Sub-Flows merge type in Flow B then, it will only merge in sub-flow C. |
Was this article helpful?
