You are here:
Classic Approval Processes Terminology
Salesforce uses this terminology for classic approval processes.
Required Editions
| Available in: both Salesforce Classic and Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions |
Approval Actions
An approval action for classic Approval Processes occurs when all required approvers approved a step.
Approval Process
A classic approval process automates how records are approved in Salesforce. A classic approval process specifies each step of approval, including from whom to request approval and what to do at each point of the process.
Approval Request
An approval request for a classic approval process is an email, Salesforce app notification, Lightning Experience notification, or Chatter post. The approval request notifies the recipients that a record was submitted for them to approve.
Approval Steps
Approval steps in a classic approval process define the chain of approval for a particular approval process. Each step determines:
- Which records can advance to that step
- Who to assign approval requests to
- Whether to let each approver’s delegate respond to the requests
The first step specifies what to do if a record doesn’t advance to that step. Later steps specify what happens if an approver rejects the request.
Assigned Approver
The assigned approver in a classic approval process is the user responsible for responding to an approval request.
Delegated Approver
A delegated approver in a classic approval process is someone appointed by an assigned approver as an alternate for approval requests.
Email Approval Response
Email approval response lets users respond to approval requests by replying to an email notification.
Initial Submission Actions
An initial submission action for a classic approval process occurs when a user first submits a record for approval using a classic approval process. By default, the record is locked.
Final Approval Actions
Final approval actions for classic approval processes occur when all required approvals were obtained.
Final Rejection Actions
A final rejection action for a classic approval process occurs when an approver rejects the request and it moves to the final rejection state.
Outbound Message
An outbound message in a classic approval process sends information to a designated endpoint, like an external service. You can configure outbound messages from Setup. Configure the external endpoint and use SOAP API to create a listener for the messages.
Process Instance
A process instance represents one instance of a classic approval process. A new process instance is created each time a record is submitted for approval using a classic approval process.
Process Instance Node
A process instance node represents an instance of an approval step in a classic approval process. The system creates a process instance node each time a record enters a step in a classic approval process. The system doesn’t create a process instance node when the record doesn’t meet the step criteria, or the classic approval process instance is completed without entering the step.
Recall Actions
A recall action occurs when a submitted approval request of a classic approval process is recalled. By default, the record is unlocked.
