Lesson 26 of 29 · All lessons
Salesforce Platform Administrator
0 of 29 complete
1ADM-201 Exam Overview
  1. 1.1ADM-201 Exam Overview
2Configuration and Setup15%
  1. 2.1Company settings, fiscal year, business hours, currency, and defaults
  2. 2.2Declarative user interface configuration
  3. 2.3User setup, licensing, and lifecycle
  4. 2.4Organization security and identity controls
  5. 2.5Sharing model, record access, and folders
  6. 2.6Profiles, permission sets, groups, and muting
3Object Manager and Lightning App Builder15%
  1. 3.1Objects, schema, and relationship architecture
  2. 3.2Fields, formulas, and field dependencies
  3. 3.3Page layouts, Lightning pages, record types, and actions
4Sales and Marketing Applications10%
  1. 4.1Leads, opportunities, sales processes, and Path
  2. 4.2Campaigns, campaign members, and lead assignment
  3. 4.3Sales productivity, scoring, forecasting, and territories
5Service and Support Applications10%
  1. 5.1Case management, queues, and case assignment
  2. 5.2Support processes, auto-response, escalation, and Einstein for Service
6Productivity and Collaboration10%
  1. 6.1Tasks, events, and activity management
  2. 6.2Chatter, groups, and internal or external collaboration
  3. 6.3Salesforce mobile app configuration and user experience
  4. 6.4AppExchange, packages, AgentExchange, and Flow awareness
7Data and Analytics Management17%
  1. 7.1Importing, updating, transferring, deleting, exporting, and backing up data
  2. 7.2Matching rules, duplicate rules, and validation rules
  3. 7.3Reports and report types
  4. 7.4Sharing, folders, and report visibility
  5. 7.5Dashboards, components, filters, subscriptions, refresh, and licensing
8Automation15%
  1. 8.1Selecting automation tools for a business scenario
  2. 8.2Flow capabilities, types, configuration, and order of execution
  3. 8.3Approval processes, criteria, approvers, and outcomes
9Agentforce8%
  1. 9.1Agentforce capabilities, use cases, security, and permissions
  2. 9.2Agent Builder, prompts, instructions, testing, and conversation preview

Section 8 · Automation · 15% of exam

8.2 Flow capabilities, types, configuration, and order of execution

2 min read Updated Nov 13, 2026

Exam objective

Describe Flow use cases and configuration, including screen flows, record-triggered flows, autolaunched flows, and order of execution.

Screen flows guide a user through screens and inputs. Record-triggered flows run when records are created, updated, or deleted according to configuration. Autolaunched flows run without screens and can be invoked by other automation or processes. Select based on whether user interaction is needed and what event starts the work. Use entry criteria to limit a record-triggered flow to relevant changes. Consider whether it should run before or after the record is saved, what records it reads or updates, and whether it can cause recursion or interact with other automation. Add fault handling where appropriate and avoid unnecessary queries or repeated updates.

Use Flow Builder tools to inspect the flow, debug representative inputs, test both expected and fault outcomes, and verify as the intended user. Order of execution matters because validation rules, flows, assignment, and other automation can affect the same transaction.

Additional concepts

Screen, record-triggered, and autolaunched flows

A screen flow guides an interactive user through inputs. A record-triggered flow starts from a configured record event and criteria. An autolaunched flow runs without a user-facing screen and can be invoked by another process. Choose based on how the work starts and whether a person must interact.

Execution and troubleshooting

Before-save and after-save record-triggered flows serve different update needs. Entry criteria help limit unnecessary runs; updates to triggering records can interact with other automation or cause repeated execution if not designed carefully. Debug with realistic inputs, inspect fault paths, and verify the result after related automation has run. A user must enter missing details before submitting a request, while a status change should trigger background routing. Use a screen flow for guided input and a record-triggered flow for the automatic response to the saved record.

In exam scenarios, identify both the trigger and whether the process requires a screen before choosing a flow type.

Key takeaways

  • Screen flows are interactive; record-triggered flows start from record events; autolaunched flows run without screens.
  • Entry criteria and order of execution affect behavior and performance.
  • Debug success and fault paths with representative records and users.

Check your knowledge

Answer exam-style Automation questions with answers and explanations.

Practice Automation
Finished this lesson? Mark it complete to track your progress.

Ready for the real exam?

Take the timed Salesforce Platform Administrator simulator: same number of questions, same time limit.

Get Complete Access