- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-29-2020 12:11 PM
I am trying to create a flow which will perform sequential approvals for a record, but it doesn't seem like Flow Designer supports this.
The scenario is a given record has 3 different people that need to approve, but sequentially. This means that Approval A should trigger first, and once that person approves, then Approval B should occur, then Approval C. Then only once all three have approved should the approval field on the record be marked as approved, but if any of them reject along the way the flow should stop and the approval on the record be marked rejected.
The behavior I am seeing when setting this up is that if you set up each approval activity to approve or reject, when the first approval is done, the record is approved then when the next approval is generated, the approval is set back to requested and this continues until the final approval leaves the approval as approved. I tried setting the first two approvals to only Reject if anyone rejects, but what happens when they're configured that way is the first approval is approved which leaves the approval field as requested but when the next approval in the sequence is generated, the approval field is changed back to Not Yet Requested and then immediately back to requested.
What I am looking to do is to have the first two approvals set the approval field to rejected if they are rejected, but if they are approved to simply leave the approval field as requested until the last approval is completed and then set the approval field value to either rejected or approved based on the outcome of that last approval.
If anyone has any insight on how to configure a flow this way it would be greatly appreciated, thank you!
Solved! Go to Solution.
- Labels:
-
flow designer
- 11,437 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-12-2023 07:27 AM
Unfortunately I haven't, the best I could do is to chain Ask for Approval actions where all but the last approval in the chain has it's approval rule set to reject when anyone rejects and the last approval is set to approve or reject when anyone rejects.
This still causes the Approval field to jump back and forth between Not Yet Requested and Requested but at the end of the day it works to create the approval chain. Just be careful that you don't have any logic running on the Approval field that is triggered when the value changes to Requested, otherwise that will trigger for each new approval that is generated.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-29-2020 01:59 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-02-2020 09:26 AM
Sachin, thank you for the reply, unfortunately this isn't the issue as the tables the approvals are for are custom tables that have not been extended from task.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-07-2022 10:16 PM
Thanks Sachin. This worked for me. I was trying for Req item table
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-02-2022 12:29 PM
Thank you Sachin, it worked for me when I turned off approval engines for Requested Item.