Approval processes combined with Flow
Key Takeaway
A flow's Submit for Approval action fails on a classic approval process that lets the submitter choose the approver manually. When an approval needs background work in other systems, use a flow approval process, and pick its type by what starts the approval.
An approval process sends a record to the right people for sign-off. Salesforce offers Classic Approval Processes and Flow Approval Processes, a newer flow-based alternative where every stage and step of the approval runs a flow. A flow can submit a record to a classic approval process. A flow approval process is itself built from flows. Scenario questions ask you to pick the right tool or combination of tools, so you need to know what each one can and can't do.
Classic and flow approval processes
A classic approval process automates how a record is approved: it defines each step, who to ask for approval, and what to do at each point.
A classic approval process for travel requests could lock each request when someone submits it. It could send requests over $2,000 to the submitter's direct manager. After the manager approves or rejects the request, the process could unlock it.
Flow Approval Processes is a modern, flow-based alternative to Classic Approval Processes. Classic processes are tied to specific objects and offer limited support for conditions. Flow Approval Processes can do the following:
- Route approvals dynamically based on data and business rules
- Trigger on record changes
- Support Apex extensibility
- Keep detailed logs for compliance and audit trails
Choose Flow Approval Processes when a record needs reviews from multiple approvers or actions across multiple systems. A flow approval process can get input from people inside and outside the company. It can also interact with internal and external systems, and it can use logic to build a path for each approval scenario.