In case of any Rejection, all remaining approvals should move to "Not required"

[Pratiksha KC]

In case of any Rejection, all remaining approvals should move to "Not required"

We have created a flow that generates approvals based on a variable:

• If the fulfiller selects one approval required and type = Individual, the system sends approval to one selected individual user.

• If the fulfiller selects two approvals required with the first type = Individual and the second type = Group, the system sends two approvals — one to the individual user and one to the group.

The issue arises when we select two approvals required (Individual + Group):

• If the individual approver rejects the RITM, the other approval(s) do not move to "Not Required" status and remain in "Requested".

• However, when the individual approver approves, the behavior works correctly.

👉How can we ensure that in case of any rejection, all remaining approvals automatically move to "Not Required" instead of staying in "Requested"?

We are facing an issue with our approval flow configuration.

When we select two approvals required, the system generates two approval requests as expected. However, even after approving one approval request, the RITM still waits for the second approval before proceeding.

How can we configure the flow so that if any one of the approvals is rejected, the RITM can move forward without waiting for the second approval?

Attaching SS of flow for the reference. 

[John Gilmore]

Because of the way you are generating the approvals they won't automatically relate the first approval and the second approval in your flows to each other. As a result you will need to create a separate flow that triggers when an approval associated with the target table has its state updated. The flow will then need to query for all other approvals associated with the same record that are not in the desired state and update them to the correct state.

If you need help on how to create the flow to do this we can help but need a bit of information on the configuration of your instance. Questions such as if the record being approved is on a custom table etc...

[Ankur Bawiskar]

@Pratiksha KC 

you will have to separate out and run parallel approval.

In your case the flow can't determine which one is approved.

Another way is you can use after update BR on sysapproval_approver table and update it to "Not Required" via script after checking the approval status.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Pratiksha KC]

Hi @Ankur Bawiskar 

The client is very particular about avoiding scripting and would like this requirement to be implemented using Flow Designer only. This requirement applies specifically to this particular item. Could you please advise how we can update our existing flow to accommodate this? I have attached screenshots for reference.

[Ankur Bawiskar]

@Pratiksha KC 

you cannot use your existing flow implementation.

As mentioned you will have to move your logic to subflow OR use scripting

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Pratiksha KC · Accepted solution]

I have found the solution and am sharing it with you. I implemented this within the same flow using flow variables, and it worked successfully. Please find the attached screenshots for reference.