cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Frequent Visitor

Use cases for "Start..." --> "Wait for an approval" VS "Start and wait for an approval"?

I'm a bit confused about when to use these related actions.

12-4-2019 4-38-48 PM.jpg

Is my commentary accurate? Are there other differences?

 

Specifically, I am trying to capture status and comments from a list of reviewers, in more-or-less real time.

The following pattern (shared by other selfless experts in this forum) works pretty well:

12-4-2019 4-49-24 PM.jpg

but it only writes the responses back to my SharePoint library properties at the end of the entire Approval process; i.e., after every Reviewer has responded.

 

I am thinking of experimenting with combinations of:

  • a Parallel approval process
  • "Start", then "Wait" -- or "Start and wait"
  • collecting and evaluating the Approved/Rejected results of each parallel process to mimic "Wait for all responses" to ultimately approve or reject the submitted file

Would any other selfless experts care to offer their hard-won experience in reply?

1 ACCEPTED SOLUTION

Accepted Solutions
Dual Super User III
Dual Super User III

If you create an approval that has multiple approvers then neither pattern will let you do anything with the replies until after everyone has replied.  The reason both patterns are supported is because occasionally you want to do other things with the approval details before sending the approval or want to do something with the approval in a parallel thread. 

 

For example, a common request is to be able to send a reminder with a link to the approval if its not completed within a particular timeframe.  Sending the reminder is easily done in a parallel branch, but you need a reference to the approval itself to be able to send a link in the reminder.  So you create the approval, then create the parallel branches.  In one branch you wait for the response and in the other you do the reminder after a pause. Unless you create it before entering the parallel branch you won't be able to send a link.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

View solution in original post

2 REPLIES 2
Dual Super User III
Dual Super User III

If you create an approval that has multiple approvers then neither pattern will let you do anything with the replies until after everyone has replied.  The reason both patterns are supported is because occasionally you want to do other things with the approval details before sending the approval or want to do something with the approval in a parallel thread. 

 

For example, a common request is to be able to send a reminder with a link to the approval if its not completed within a particular timeframe.  Sending the reminder is easily done in a parallel branch, but you need a reference to the approval itself to be able to send a link in the reminder.  So you create the approval, then create the parallel branches.  In one branch you wait for the response and in the other you do the reminder after a pause. Unless you create it before entering the parallel branch you won't be able to send a link.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

View solution in original post

Dual Super User III
Dual Super User III

Just to add to my reply.   Using either action to create and wait for the approval works the same way.  You'll need to do each approval separately in a parallel branch.  All the parallel branches will need to finish before the flow will be able to move on.  But you will be able to do things inside each branch to react to the individual approvals.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Helpful resources

Announcements
Microsoft Ignite

Microsoft Ignite

Join digitally, March 2–4, 2021 to explore new tech that's ready to implement. Experience the keynote in mixed reality through AltspaceVR!

New Super Users

Meet the Power Automate Super Users!

Many congratulations to the Season 1 2021 Flownaut Crew!

Microsoft Ignite

Microsoft Power Platform: 2021 Release Wave 1 Plan

Power Platform release plan for the 2021 release wave 1 describes all new features releasing from April through September 2021.

MPA Community Blog

Power Automate Community Blog

Check out the community blog page where you can find valuable learning material from community and product team members!

Users online (41,758)