Specify Rejection Behavior for an Approval Step in a Classic Approval Process
Configure what happens if an approver rejects a request. The final rejection actions
for the classic approval process determine the first step’s rejection behavior.
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.
Option
Description
Perform all rejection actions...
Rejects the request even if
previous steps were approved. Salesforce performs all rejection actions specified
for this step and all final rejection actions.
Perform ONLY the rejection actions for this
step...
Rejects the request, and
returns the approval request to the previous approver. Salesforce performs all
rejection actions specified for this step.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.