Loading
Connect in real time with the Trailblazer Community in Slack Open BetaRead More
Automate Your Business Processes with Salesforce Flow
Limits and Considerations for Classic Approval Processes

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
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.

Users with Modify All Data can submit records even if they aren’t initial submitters. If an initial submitter is a group with Grant Access Using Hierarchies enabled, only direct members of the group can submit. For details, see Specify Who Can Submit Records to a Classic Approval Process.

 
Loading
Salesforce Help | Article