How to perform sequential approvals in Flow Designer?

[Jordan26]

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!

[parth2]

Hi,

Please check Sachin's reply below. That helped me

[-O-]

You should open a new thread for this. You are not the original poster, therefore you cannot accept something as an answer, therefore point-hunters cannot benefit (rack up points) from answering your problem, therefore most probably nobody will.

Plus saying "I have the same issue" in response to an answer that does not describe solutions is in no way indicative of what is your problem. How could anyone help you without knowing where you need help?

[Jordan26]

I was the one who accepted it as the solution, not arizeciri.

[-O-]

Yes, I know, but my post was a reply to @arizeciri not you 🙂

[Jan60]

Flow supports a "Lookup Records" action, which you can use to identify the approvers yourself using user or group references.

These "Looked up records" are available as data pil in "Ask for approval" and you may apply approval rules like "Anyone" or "All" or "% of". You also may split between rules for approvals and rules for rejection.
If you would like to establish a sequence, you may embrace "Ask for approval" with a for-reach, where the for-each action refers to the records you looked up.

You may react to the approval or rejection with an if-step after the "Ask for approval".

In case of rejection I would suggest to reset all previous approvals to "Cancelled", otherwise the workflow always follows the rejection path as soon as there is just one rejected item in the approval history.

Please see the article, which provides an overview about different use cases:

https://www.servicenow.com/community/workflow-automation-articles/flow-designer-approvals-overview-w...