Approval Flow - "everyone must approve" - Visibility into approvers

[macd909]

Hi All,

I am very new to microsoft flow. I am trying to re-create a document approval flow which we originally used in sharepoint 2007 using power flow as we have recently migrated to sharepoint online.

The approval flow is always to the same 2 approvers and both must approve the document before it is approved. I have got this working correctly however if there is a delay in the approval/rejection (which there often is) the requestor doesn't have any visibility of which of the 2 approvers is left to action (could be both, could just be one). This means the requestor doesn't know who to chase. The visibility of the approvers' actions only becomes visible when both have responded. This useful functionality was available on the sharepoint workflows so it would be nice to somehow present this information. 

Thanks in advance of any tips!

Greg

[Pstork1]

For your scenario you would run two separate approval actions in parallel, one for each user.  The flow won't consider the approval complete until both approve.  But that will allow sending an email to the requestor as each approver approves their approval.

[macd909]

Many thanks for the pointer. I have set up the parallel approval actions and the independent emails for each user are working.

Now the approvals are split, I am now trying to figure out how I can have the flow stop immediately if either of approvers choose to reject? 

I would also like to send an "approved confirmation email" once both approves have approved but I am not sure if there is a way to verify the output of both approvals with a single step?

Thank you!

[Pstork1]

There are two ways to have the flow stop immediately if one of the approvers reject.

1) You could add a terminate to each parallel branch that would terminate the flow when the approval is rejected.  This will work, but won't cleanup the other approvals so I don't recommend it.

2) You can delete the remaining approval using CDS.  That won't clean up the email, but will clean up other artifacts from the approval.  This is the better way to go but it is a premium function.  It also takes extra work since you'll have to use Create Approval actions to create both approvals before entering the parallel branches and then use just Wait for approvals in those branches.  The separate creates are so you can access the Approval ID in the parallel branches to delete the approvals in CDS.