Flow Approval processes versus classic approval processes
Key Takeaway
A flow approval process is a flow-based alternative to a classic approval process that supports dynamic routing. One known gap is that only classic approval processes can let the submitter choose the next approver manually.
An approval process sends a record to the right people for sign-off before it moves forward. Salesforce offers two tools for this. Classic approval processes define a fixed series of approval steps for an object. Flow approval processes are a newer flow-based alternative that mixes human approvals, automated background actions and conditional paths. App builders need to know where each tool fits and the known gaps between them.
Classic approval processes
A classic approval process automates how records are approved by defining each step: who to ask for approval and what to do at each point.
For example, imagine an expense process. It first locks the record and sets its status to Submitted. It auto-approves amounts of $50 or less and sends larger amounts to the direct manager. It then adds a vice president approval above $5,000. Finally, it sets the status to Approved or Rejected and unlocks the record.
The word "classic" does not mean Salesforce Classic only. Classic approval processes are available in both Salesforce Classic and Lightning Experience, in these editions:
- Enterprise Edition
- Performance Edition
- Unlimited Edition
- Developer Edition