Power Apps makers use the approval pattern to ensure that data, decisions, and documents are reviewed by a stakeholder or multiple stakeholders, either all at once or in sequence. Although the approval pattern can be valuable on its own, it's frequently combined with other patterns, especially the inspection or audit pattern. Approvals can be easily implemented with Power Automate approval workflows, but can also be implemented with capability you build into your app.

In a typical approval scenario:

  1. Data is collected from user input, external systems, or other sources. The data might be a document, multiple documents, a single value, or the results from another system. The user initiates a request for approval, or the system might automatically initiate an approval based on criteria (for example, purchases over $1,000 require approval) or scenario (for example, international travel requires executive approval).
  2. An approver, or multiple approvers, evaluates the information and takes action that does one of the following:
    • Advances the request to another approver.
    • Approves the request.
    • Reassigns the request to another person.
    • Rejects the request.
  3. The system takes action based on the response of the approver.
© 2004-2024 Amidus