Each classic approval process is organized into groups of actions based on when the actions occur, such as initial submission. To add an automated action to your classic approval process, determine which group of actions to add it to.
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.
| Group | Occurs When... | Default Actions |
|---|---|---|
| Initial Submission | A user first submits a record for approval. | Record Lock (locks) |
| Approval Step Approval | All required approvals for this step have been given for a record. | None |
| Approval Step Rejection | An approver rejects this request for this step. | None |
| Final Approval | All required approvals have been given for a record | Record Lock (locks) |
| Final Rejection | An approver rejects the request, and it goes to the final rejection state. | Record Lock (unlocks) |
| Recall | A submitted approval request is recalled. | Record Lock (unlocks) |