You are here:
Limits and Considerations for Classic Approval Processes
Before you automate something with a classic approval process, be aware of the limits and considerations.
Required Editions
| Available in: both Salesforce Classic and Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions |
Important Try Flow
Approval Processes, a modern alternative to Classic Approval Processes. This new
feature provides a more flexible, user-friendly flow-based interface, and it can trigger on
record changes, supporting Apex extensibility and detailed logging for compliance and audit
trails. It supports dynamic routing based on data and business rules, unlike Classic Approval
Processes, which are tied to specific objects and offer limited support for processes by using
conditions. With Flow Approval Processes, you can monitor submitted records and quickly
identify bottlenecks, giving you unprecedented visibility into approval workflows. And, like
Classic Approval Processes, Flow Approval Processes don’t consume automation credits or
orchestration runs.
Users can’t see which classic approval process is triggered when they click Submit for Approval. Familiarize users on the criteria for each classic approval process and what each classic approval process does. If the record doesn’t meet the entry criteria or if they’re not an allowed submitter for any classic approval processes, Salesforce displays an error.
- Classic Approval Processes Limits
Salesforce limits the number of classic approval processes in your org, as well as the number of steps and actions in each classic approval process. - Considerations for Configuring Classic Approval Processes
When creating or editing a classic approval process, keep in mind how approvals are compatible with other features. Before you start, draw out the steps of your classic approval process. - Merge Fields for Classic Approval Processes
Approval merge fields include {!ApprovalRequest.fieldName} and {!Approval_Requesting_User.fieldName}. They’re supported in certain email templates and return different values based on the status of the classic approval process instance. - Considerations for Setting Approvers in Classic Approval Processes
When you specify approvers for a given approval step—or for the only step if you’re using the jump start wizard—keep these considerations in mind. - Considerations for Managing Classic Approval Processes
Keep these things in mind when maintaining existing classic approval processes—including activating and deleting them. - Classic Approval Process Considerations for the Salesforce Mobile App
Learn about the classic approval processes functionality in Lightning Experience on desktop that isn’t available or that works differently in the Salesforce mobile app.
See Also
- Flow Approval Processes Limits and Considerations
- Considerations for Email Approval Response in Classic Approval Processes
- Considerations for Classic Approval Processes in Chatter
- Approvals: What’s Different or Not Available in the Salesforce Mobile App
- Considerations for Classic Approval Process History Reports
- Restrictions for Approval Processes in Change Sets
Did this article solve your issue?
Let us know so we can improve!
