Study guide

7.2 Flow Builder: Screen, Record-Triggered, Scheduled, and Autolaunched Flows

Salesforce Admin Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Platform Administrator Orientation and Official Source Control

1.1 Credential Name, Current Outline, and Search Language 1.2 Exam Format, Fee, Score, and Reference Rules 1.3 Trailhead, Trailhead Academy, and Pearson VUE Delivery Workflow 1.4 Domain Weights, Agentforce, and Study Prioritization 1.5 Maintenance Modules, Credential Ethics, and Exam Security 1.6 Developer Edition, Trailhead Playground, and Practice Bank Workflow

2 Chapter 2: Configuration, Setup, User Management, and Org Controls

2.1 Company Information, Fiscal Year, Business Hours, and Locale 2.2 User Records, Licenses, Profiles, Permission Sets, and Login Access 2.3 Login Security, Session Settings, and Identity Basics 2.4 Setup Navigation, Release Readiness, and Change Control 2.5 UI Settings, Home Pages, Apps, and Navigation 2.6 Configuration and Setup Case Lab

3 Chapter 3: Security, Access, Identity, and Sharing Model

3.1 Org-Wide Defaults, Roles, Sharing Rules, and Teams 3.2 Profiles, Permission Sets, Permission Set Groups, and Muting 3.3 Field-Level Security, Page Layouts, and Dynamic Forms 3.4 Record Access Troubleshooting and Login-As Workflow 3.5 Identity, Login History, MFA, and Session Risk 3.6 Data Visibility, Reporting, and Analytics Security 3.7 Security and Access Case Lab

4 Chapter 4: Object Manager, Lightning App Builder, and Data Modeling

4.1 Standard Objects, Custom Objects, and Schema Fit 4.2 Fields, Formulas, Rollups, Validation, and Requiredness 4.3 Lookup, Master-Detail, and Junction Relationships 4.4 Record Types, Business Processes, Page Layouts, and Lightning Pages 4.5 Dynamic Forms, Dynamic Actions, and User Experience 4.6 Schema Change Risk, Data Quality, and Deployment Readiness 4.7 Object Modeling Case Lab

5 Chapter 5: Sales, Marketing, Service, and Support Applications

5.1 Lead, Campaign, Account, Contact, and Opportunity Flow 5.2 Sales Processes, Path, Products, Price Books, and Forecasting 5.3 Case Management, Queues, Assignment, Auto-Response, and Escalation 5.4 Knowledge, Entitlements, Service Console, and Support Productivity 5.5 Sales-Service Data Quality and Automation Boundaries 5.6 Application Configuration Troubleshooting 5.7 Sales and Service Applications Case Lab

6 Chapter 6: Data and Analytics Management

6.1 Data Import Wizard, Data Loader, Export, and Backup 6.2 Duplicate Management, Validation, and Data Quality Controls 6.3 Data Transfer, Ownership, Mass Update, and Mass Delete 6.4 Report Types, Filters, Summary Formulas, and Buckets 6.5 Dashboards, Components, Subscriptions, and Sharing Impact 6.6 Analytics Security, Visibility, and Executive Reporting 6.7 Data and Analytics Case Lab

7 Chapter 7: Automation, Flow, Approval, and Operational Processes

7.1 Automation Tool Selection and Order of Execution 7.2 Flow Builder: Screen, Record-Triggered, Scheduled, and Autolaunched Flows 7.3 Approval Processes, Email Alerts, and Notification Patterns 7.4 Validation Rules, Assignment Rules, and Escalation Rules 7.5 Automation Testing, Debugging, and Governance 7.6 Automation Performance, Recursion, and Maintainability 7.7 Automation Case Lab

8 Chapter 8: Productivity, Collaboration, Mobile, and AppExchange

8.1 Activities, Tasks, Events, Calendar, and Email Productivity 8.2 Chatter, Feeds, Groups, Notifications, and Collaboration Governance 8.3 Salesforce Mobile Navigation, Actions, and Page Design 8.4 List Views, Kanban, Path, and User Adoption Tools 8.5 AppExchange Evaluation, Installation, Permissions, and Risk 8.6 Productivity and Collaboration Case Lab

9 Chapter 9: Agentforce for Platform Administrators

9.1 Agentforce Use Cases, Admin Boundaries, and Fit 9.2 Trusted AI, Security, Data Access, and Permission Implications 9.3 Agent Builder, Prompt Builder, and Grounding Concepts 9.4 Testing, Deployment, Monitoring, and Feedback Workflows 9.5 Agentforce Service, Sales, and Internal Productivity Scenarios 9.6 Agentforce Risk, Troubleshooting, and Governance 9.7 Agentforce Case Lab

10 Chapter 10: Integrated Salesforce Admin Scenario Labs

10.1 New Sales Org Setup Integrated Lab 10.2 Service Team Case Management Integrated Lab 10.3 Data Quality and Analytics Integrated Lab 10.4 Security, Access, and Reporting Integrated Lab 10.5 Flow Automation and Change Control Integrated Lab 10.6 Agentforce and Adoption Integrated Lab 10.7 Full Admin Simulation Strategy

11 Chapter 11: Final Review, Maintenance, and Test-Day Strategy

11.1 Final 30-Day Salesforce Admin Review Plan 11.2 Trailhead Playground Hands-On Drill Plan 11.3 105-Minute Exam Timing, Flagging, and Review Workflow 11.4 Test-Day Checklist: Online or Test Center 11.5 Post-Exam Maintenance Modules and Next Certifications 11.6 Salesforce Admin Final Mixed Review

7.2 Flow Builder: Screen, Record-Triggered, Scheduled, and Autolaunched Flows

Key Takeaways Explain This Topic AI

Screen flows are for guided user interaction, while record-triggered, scheduled, and autolaunched flows are for background automation patterns.

Before-save and after-save record-triggered flows solve different problems and should be chosen based on whether the automation changes the triggering record or other work.

Flow Builder design must account for permissions, data access, fault paths, bulk behavior, user experience, and version control.

Debugging and testing flows means proving both the happy path and the failure path before activation.

Last updated: May 2026

Flow types and when they fit

A screen flow is an interactive experience. It can ask questions, show choices, validate user input, create records, update records, and branch based on values. Use it when the user needs guidance, when the process spans several objects, or when the standard page layout cannot express the decision path clearly. A screen flow can be launched from a Lightning page, quick action, utility bar, Experience Cloud site, or other supported entry point.

A record-triggered flow runs because a record changes. It can run when a record is created, updated, deleted, or meets criteria. Before-save flows are efficient for changing fields on the same record. After-save flows are needed when the flow must create related records, update other records, send notifications, call actions, use the saved record ID, or run paths after the record is committed. Entry criteria should be narrow enough to avoid needless interviews.

A scheduled-triggered flow runs at a configured date and time and can select records that meet criteria. It is useful for recurring maintenance such as creating renewal tasks, marking stale onboarding items, or checking records that need follow-up. It should not be used as a substitute for real-time automation when users expect immediate results. Scheduled flows also need volume judgment because they can process many records at once.

An autolaunched flow has no screen and can be called by other automation, Apex, buttons, actions, external integrations, or another flow as a subflow. It is useful for reusable logic, such as calculating a service entitlement result or creating a standard set of onboarding records. Reuse is valuable only when the input and output contract is clear. A vague subflow can spread risk across many callers.

Flow design aid

Flow type Best use Design questions

Screen flow Guided user process Who runs it, where is it launched, what permissions are needed, and how are errors shown?

Before-save record-triggered flow Same-record field updates Can the value be set before validation and save, and can criteria prevent extra runs?

After-save record-triggered flow Related records and actions What objects are touched, what faults are possible, and can it recurse?

Scheduled-triggered flow Recurring record checks How many records can match, what happens on holidays, and who monitors failures?

Autolaunched flow Reusable background logic What inputs are required, what outputs are returned, and which callers depend on it?

Subflow Shared logic inside another flow Is the shared behavior stable enough to reuse safely?

Flow Builder is reached from Setup > Process Automation > Flows . A practical admin also knows where the flow is used. A flow may be on a Lightning record page, invoked by a button, referenced by a quick action, started by another flow, called from Apex, or exposed through automation settings. Before editing, inspect activation status, latest version, dependencies, and where-used information where available.

Decision elements should read like business policy. Instead of a decision named Check 1, use names such as Discount Requires Approval or Case Needs Premium Escalation. Outcomes should be mutually understandable, and the default outcome should be deliberate. Assignment elements should have clear variable names. Get Records elements should retrieve only the fields and rows needed. Collection variables should be used when multiple records must be updated together.

Fault handling is not optional in serious flows. Record creates and updates can fail because of validation rules, missing permissions, duplicate rules, locked records, lookup filters, required fields, or data type problems. A screen flow should show a helpful error or recovery path. A background flow should use fault connectors where useful, log details to an admin-owned object or platform event when the org has that pattern, and avoid hiding failures from operations.

Build, test, and activate with discipline

Flow testing should start in a Trailhead Playground, Developer Edition org, or sandbox before production. Create sample records for each branch, including records that should not enter the flow. Test as users with different permissions when the flow runs in user context or when field-level security matters. If the flow updates records the user cannot normally edit, understand whether system context is appropriate and document the reason. Running everything in elevated context can create security surprises.

A focused flow build workflow:

Write the business trigger, entry criteria, expected outputs, and exception path.

Choose the flow type and context that fit the requirement.

Build the smallest viable flow with clear element names.

Add fault paths for record operations and user-facing error handling for screen flows.

Debug with records that cover every decision outcome.

Test bulk updates, import behavior, validation conflicts, and user permissions.

Activate a new version during a controlled release window and monitor failures.

Screen flows need user experience care. Do not show every possible field just because the data exists. Use choice sets for controlled options, required inputs where the step cannot continue without data, and clear labels that match business terms. Keep screens short, group related fields, and avoid asking users for data Salesforce can derive. If the flow creates records, show a confirmation or navigate the user to the result.

Record-triggered flows need recursion care. If a flow updates the same object that triggered it, it may cause another save and another interview unless criteria or change checks stop it. Use entry conditions such as only when a record is updated to meet the condition, compare prior values where available, and avoid updating the triggering record in after-save flows when before-save logic would work. Document intentional re-entry.

Scheduled flows need operational ownership. Someone must know when they run, how many records they process, what happens on failure, and what reports prove they worked. If a scheduled flow sends notifications, create guardrails so users are not spammed after a data load. If a scheduled flow changes statuses, test records near boundary dates and time zones. Automation is successful only when the operations team can understand and support it after activation.