Study guide

7.7 Automation Case Lab

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.7 Automation Case Lab

Key Takeaways Explain This Topic AI

A case lab turns automation theory into an end-to-end admin workflow with routing, validation, flow, notifications, testing, and monitoring.

The strongest lab design uses purpose-built features first and adds Flow only where it improves the process.

Hands-on practice should include realistic records, multiple users, queue ownership, failed-path testing, and bulk-safe behavior.

A finished automation case includes documentation, release controls, support ownership, and post-release validation.

Last updated: May 2026

Lab scenario: premium support triage

Use a sandbox, Developer Edition org, or Trailhead Playground for this practice. The business scenario is a service team that supports standard and premium customers. New premium cases should route to a Premium Support queue. Sev 1 cases should notify a support manager and create an urgent follow-up task. Cases cannot move to Working until Product Family is populated. Cases that remain New for four business hours should escalate to the manager queue. The team wants a simple guided action for agents to classify a case and capture the first response.

This scenario is intentionally mixed. It should not become one enormous flow. Case assignment rules are a natural fit for initial queue routing. A validation rule is a natural fit for blocking status movement without Product Family. A case escalation rule can handle aged New cases if the requirement matches standard escalation behavior. A screen flow can guide agents through classification and first response. A record-triggered flow can create the urgent task and notification for Sev 1 cases if assignment and escalation rules do not cover that action cleanly.

Start by writing the process in plain language. New cases arrive from Email-to-Case, web forms, and manual creation. Premium status is stored on Account or on a case field copied from Account. Severity is a case picklist. Product Family is required before work begins. Agents work from queues. Managers need alerts for urgent cases but should not receive duplicate messages every time a case is edited. These statements become your design constraints.

The lab is successful when you can explain why each tool is used. If you choose Flow for everything, you miss the purpose-built features. If you avoid Flow entirely, the guided agent experience and task creation may be clumsy. The admin skill is balanced selection.

Build plan and setup checklist

Requirement Recommended feature Validation question

Route premium cases to a queue Case assignment rule Does the entry point invoke the active assignment rule?

Block Working status until Product Family is set Validation rule Does the rule work from UI, import, Flow, and API updates?

Escalate New cases after four business hours Case escalation rule Are business hours and actions configured correctly?

Guide agents through first response Screen flow Can target users run it and update required fields?

Create urgent task for Sev 1 Record-triggered flow Does it run only once and avoid duplicate tasks?

Notify manager for urgent cases Custom notification or email alert Does the manager have record access and useful context?

Setup checklist:

Create or confirm a Premium Support queue for cases and add test members.

Create a support manager test user or identify a safe existing test user in the sandbox.

Confirm Case fields for Severity, Product Family, Account, Status, and any Premium indicator.

Build a case assignment rule entry that routes premium cases to the queue.

Build a validation rule that blocks Status equals Working when Product Family is blank.

Configure escalation behavior for New cases that exceed the business-hour threshold.

Build a screen flow that lets an agent classify Product Family, enter first response notes, and move Status to Working.

Build a record-triggered flow for Sev 1 task and notification behavior with criteria that prevent duplicates.

The Sev 1 flow needs careful design. It should run when a case is created or updated to meet Severity equals Sev 1 and perhaps when Urgent Task Created is false. It should create one task assigned to the right owner or queue and set a flag to prevent re-creation. If that flag update is on the same record, consider whether before-save or after-save timing fits the whole design. Because task creation requires an after-save action, you may use after-save flow but must prevent recursion with criteria and a flag.

Test script, release notes, and study judgment

Run the lab with at least five records. Create a standard case and confirm it does not route to Premium Support. Create a premium case and confirm assignment. Create a premium Sev 1 case and confirm the urgent task and notification are created once. Try to move a case to Working without Product Family and confirm the validation message is clear. Use the screen flow to classify the case and confirm the status update succeeds. Create a case that should escalate and test the rule timing in the safest available way for the environment.

Test as different users. The system administrator can usually do everything, but agents and managers may have narrower permissions. Confirm queue members can see and accept cases. Confirm the manager can open the notified record. Confirm the screen flow is available from the Lightning page or action where agents expect it. Confirm field-level security allows users to read and edit fields the flow displays. A flow screen that shows a field the user cannot use is a design bug, not just a permission bug.

Bulk and failure tests matter. Import or update a small set of cases to simulate channel volume. Confirm the assignment rule behavior for the entry point you choose. Confirm the Sev 1 flow does not create duplicate tasks when records are edited again. Force a validation failure by leaving Product Family blank. Try a locked or closed case if that state exists in the org. Review failed flow interviews, task lists, queues, and notification volume after testing.

Lab documentation template:

Business purpose: premium support triage and urgent response.

Tools used: case assignment rule, validation rule, escalation rule, screen flow, record-triggered flow, notification action.

Objects touched: Case, Task, Account if premium status is read, User or Queue for ownership.

Entry criteria: premium indicator, Severity equals Sev 1, Status equals New, Status changes to Working.

Bypass or exception: documented admin-only data repair path if needed.

Monitoring: queue reports, aged case report, urgent task report, failed flow interviews, manager feedback.

For study purposes, focus on the reasoning. A scenario that says route cases should point you toward assignment rules before custom flow. A scenario that says block save should point to validation. A scenario that says guide an agent should point to screen flow. A scenario that says approval, lock, and approve should point to approval process. The case lab trains you to combine features while keeping each feature in its strongest lane.