The primary differences between using Start and Wait for an Approval and Create an Approval with the Wait for an approval action are:
-
Start and Wait for an Approval automates the full lifecycle of the Approval. It creates the records in CDS, send notifications, and then blocks the flow run until the Approval criteria is met or the action times out. The outputs of the action include the approvers, responses, comments, etc. because the approval is guaranteed to be complete at the time that the next step runs in the Flow.
-
Create an Approval will create the records in CDS and send notifications, but will NOT block execution of the Flow. Responses, approvers, comments, etc. are NOT available as outputs for use in other steps, because the approval is not guaranteed to be complete. Flow authors will need to use the Wait for an approval step to gather the responses, approvers, comments and any other data gathered as part of the approval being approved or rejected.
|
|
Start and Wait for an approval |
Create an Approval |
|
Creates records in CDS |
Yes |
Yes |
|
Basic email notifications (including actionable email) and push notifications to the Flow Mobile app |
Yes |
Yes |
|
Responses/comments available as outputs |
Yes |
No, use Wait for an Approval to use these in the Flow. |
|
Step outputs an adaptive card that can be posted to Microsoft Teams |
No, the approval is already complete after this step completes. |
Yes |
If you:
Want to store extra data in SQL, CDS, etc. that contains approver information at the time of the request?
-
Use Create an Approval, add steps that log the approval information, then Wait for an approval
Want to send adaptive cards to users in Microsoft Teams for them to approve directly within the Teams client?
-
Use Create an Approval, an in an Apply To Each over the approvers, use the Teams connector Flow bot action to post the adaptive card output from Create An Approval to each user, and then Wait for an approval.