Automation15% of the exam
Approval processes from submission to final action
How a classic approval process is built and behaves: entry criteria, allowed submitters and recall, record locking and editability, approval steps with step criteria and approver options, rejection behavior, the four action types, activation rules, and where Flow Approval Processes fit.
Describe capabilities, use cases, and configuration for the approval process (criteria for approvers, rejections, approvals).
~8 min read · 11 practice questions ·
What the exam expects
- Configure who can enter an approval process: entry criteria, allowed submitters, and whether submitters can recall their own requests.
- Explain record locking and choose the record editability option that fits.
- Build approval steps: step criteria, what happens when they aren't met, and the approver options.
- Configure rejection behavior per step and the action groups (initial submission, step, final approval, final rejection, recall) and know which four action types are allowed.
- Know activation and deletion rules, where approval progress is visible, and when to hand off to Flow.
Key facts
Permission to build
- Detail
- Customize Application
Default approver option
- Detail
- Let the submitter choose manually
Approvers per step
- Detail
- Up to 25 users, queues or related users; first response or unanimous
Default record editability
- Detail
- Administrators ONLY
Approval admins
- Detail
- Modify All Data, or Modify All Records on the object
Recall off
- Detail
- Only admins can recall requests
"reject record" for unmatched step criteria
- Detail
- First step only
Action types
- Detail
- Task, Email Alert, Field Update, Outbound Message
Action groups
- Detail
- Initial submission, step, final approval, final rejection, recall
Adding steps
- Detail
- Only while the process is inactive
Deleting a process
- Detail
- Must be inactive first
Sources for this section (7)
- Approval Wizardhelp.salesforce.com (opens in a new tab)
- Assigned Approvershelp.salesforce.com (opens in a new tab)
- Record Editabilityhelp.salesforce.com (opens in a new tab)
- Managing Approval Processeshelp.salesforce.com (opens in a new tab)
- Approval Submittershelp.salesforce.com (opens in a new tab)
- Approval Step Criteriahelp.salesforce.com (opens in a new tab)
- Approval Actionshelp.salesforce.com (opens in a new tab)
- Why can't a rep edit an opportunity right after submitting it, and which record editability option is the default?
- Which three choices do you have for records that don't meet an approval step's criteria, and which one is limited to the first step?
- When would you use one step with unanimous approval instead of a queue?
- Which four action types can a classic approval process run, and how do you get Flow logic to run after final approval?
- What can't you change in an approval process after it has been activated once?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Platform Administrator pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 28 lessons of the Platform Administrator guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (11 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams