You are here:
Add Automated Actions to a Classic Approval Process
You can associate actions to approval steps, initial submission, final approval, final rejection, or recall. Classic approval processes support four automated actions.
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.
| Action Type | Description |
|---|---|
| Task | Assigns a task to a user who you specify. You can specify the subject, status, priority, and due date of the task. |
| Email Alert | Sends an email to a designated recipient using a specified email template. |
| Field Update | Changes the value of a selected field. You can specify a value or create a formula for the new value. |
| Outbound Message | Sends a message to a designated endpoint. You can also specify a username and the data to include in the message. Not supported for classic approval processes on junction objects. |
Example
When expenses are approved, you want to print checks for payment. To do so, you add an outbound message, which sends the appropriate information to your Oracle accounting service, as a Final Approval action.
- Groups of Automated Actions in a Classic Approval Process
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. - Add an Automated Action to Your Classic Approval Process
If you didn’t create an automated action before configuring your classic approval process, you can create one directly from the classic approval process. - Add an Existing Automated Action to Your Classic Approval Process
If you’ve already created an automated action, you can add it to your classic approval process.
Did this article solve your issue?
Let us know so we can improve!
