Study guide

7.1 Automation Tool Selection and Order of Execution

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.1 Automation Tool Selection and Order of Execution

Key Takeaways Explain This Topic AI

Choose automation tools by entry point, timing, user interaction, bulk volume, error handling, and long-term ownership.

Order of execution explains why validation, duplicate rules, assignment rules, flows, approval actions, and save behavior can interact in surprising ways.

Modern admin automation judgment favors Flow for most declarative automation, but not every problem should become a flow.

A safe design includes criteria discipline, bulk testing, recursion controls, monitoring, and a documented rollback or disable plan.

Last updated: May 2026

Tool selection starts with the business event

Automation should begin with a precise sentence: when this business event happens, Salesforce should do this outcome, for these records, under these conditions. That sentence tells the admin whether the automation needs a screen, a record save, a schedule, an approval gate, a notification, a routing rule, or a human checklist. If the event is vague, the tool choice will be fragile.

Flow is the main declarative automation platform for modern admins. Screen flows guide users through interactive steps. Record-triggered flows run when records are created, updated, or deleted. Scheduled-triggered flows run at a chosen cadence. Autolaunched flows can be invoked by other automation, buttons, actions, Apex, external calls, or orchestrated processes. Flow is powerful, so the admin must design it like production logic.

Not every request belongs in Flow. A formula field is better when the result is derived and does not need storage. A validation rule is better when the goal is to block a bad save with a clear message. An approval process is better when a record must be locked, routed, approved, rejected, and audited through a formal gate. Assignment and escalation rules are still purpose-built for lead and case operations.

Setup navigation is part of hands-on readiness. Flows are managed from Setup > Process Automation > Flows . Approval processes are configured from Setup > Process Automation > Approval Processes . Validation rules are under Object Manager > Object > Validation Rules . Lead and case assignment rules, case escalation rules, email alerts, and classic workflow actions live in Setup areas tied to their feature families.

Decision table and order awareness

Need Better starting point Why

Guide a user through data entry Screen flow It can show screens, collect values, branch, and create or update records.

Update related records after a save Record-triggered flow It reacts to record changes and can run before or after save depending on the need.

Block a record that violates policy Validation rule It gives a deterministic save-time error and works across UI, import, and API paths.

Route leads or cases to owners Assignment rule It is built for lead and case ownership routing and can work with queues.

Require manager signoff Approval process It supports submission, locking, approval steps, rejection actions, and audit history.

Send time-based case follow-up Escalation rule or scheduled flow Choose based on whether the case SLA model or a broader automation pattern is required.

Show a derived value Formula field It avoids stored data and automation limits when no action is required.

Order of execution is the reason simple automations collide. A record save can trigger system validation, before-save flows, custom validation rules, duplicate rules, after-save flows, assignment rules, auto-response rules, workflow actions, process-style actions in legacy orgs, escalation logic, roll-up calculations, sharing evaluation, and commit behavior. The exact platform sequence is detailed, but admin judgment focuses on what can change values before validation, what can still fail the transaction, and what might cause another save.

Before-save record-triggered flows are usually preferred for same-record field updates because they are fast and avoid an extra database update. After-save flows are used when the flow must create related records, update other records, send notifications, call subflows that need saved IDs, or perform actions that require the record to exist in the database. A common trap is using after-save logic for a same-record update that could be handled before save.

Automation should be designed to be bulk-safe. A flow that works for one opportunity edit can fail when Data Loader updates 10,000 opportunities. Avoid Get Records inside loops when one query can collect data first. Avoid Update Records inside loops when records can be collected and updated once. Consider scheduled paths, async paths, and batch size effects when operations could hit limits.

Scenario judgment and admin controls

Imagine a sales operations manager asks for this: when a high-discount opportunity moves to proposal, require approval, notify the deal desk, create a task for legal if the amount is above a threshold, and prevent the sales rep from closing the deal until approval is complete. This is not one tool. The approval process handles submission, approvers, locking, and final approval or rejection actions. A validation rule or flow entry condition can prevent Closed Won when approval status is not approved.

A record-triggered flow can create the legal task after submission or status change if the requirement is outside the approval action pattern.

A simpler request may not need automation at all. If a manager wants a reminder that renewal opportunities need a next step, a required field on a path stage, a validation rule, or report subscription may be easier to support than a new flow. If the team wants a calculated renewal risk score, a formula may be enough until the score must create work or integrate with another system. Good admins reduce automation when metadata or reporting can solve the need cleanly.

Admin-safe checklist:

Name automation with object, event, and outcome so future owners can scan it.

Document entry criteria, fields updated, related objects touched, and expected exceptions.

Test create, update, bulk update, import, integration user, and permission edge cases.

Decide how to pause, deactivate, or bypass automation during data repair.

Monitor failed flow interviews, email deliverability, approval queues, and user feedback after release.

Keep Agentforce and AI actions behind clear permissions, trusted data grounding, and human review when outcomes affect records.

Agentforce can surface actions, guide support, and help users find next steps, but deterministic record changes still need controlled automation. Do not use an AI agent to make a compliance decision that should be an approval process, a validation rule, or a policy-controlled flow. The admin boundary is to configure access, data grounding, action permissions, testing, monitoring, and fallback paths. If the result must be repeatable and auditable, use a governed automation pattern and let AI assist rather than decide.

Study scenarios often hide the tool behind wording. Look for words such as guide, route, approve, block, calculate, notify, schedule, assign, escalate, and integrate. Then ask whether the action is interactive, synchronous, asynchronous, save-blocking, bulk, cross-object, or approval-based. The best answer is usually the smallest durable tool that satisfies the business control without creating hidden operational debt.