Shopping cart

Subtotal:

$0.00

ADM-201 Automation

Automation

Detailed list of ADM-201 knowledge points

Automation Detailed Explanation

Salesforce's automation features help streamline workflows, reduce manual effort, and ensure consistency in business processes. By leveraging automation, organizations can improve efficiency and enhance user productivity.

8.1 Workflow Rules

Workflow rules are one of Salesforce's simplest automation tools, designed to trigger specific actions when conditions are met.

What Are Workflow Rules?

  • Automation rules that execute predefined actions based on certain criteria.
  • Consist of two main parts:
    1. Criteria: The condition that must be met for the rule to trigger.
    2. Actions: What the system does when the criteria are met.

Types of Workflow Actions

  1. Field Updates:

    • Automatically update a field’s value.
    • Example: Set the "Status" field to "Closed" when an Opportunity is won.
  2. Email Alerts:

    • Send automated emails to users or external recipients.
    • Example: Notify the manager when a high-value Opportunity is created.
  3. Tasks:

    • Create a task and assign it to a user.
    • Example: Assign a follow-up task to a sales rep when a Lead is converted.
  4. Outbound Messages:

    • Send data to external systems via an API.
    • Example: Notify an external billing system when an invoice is generated.

How to Create a Workflow Rule

  1. Go to Setup and search for Workflow Rules.
  2. Click New Rule.
  3. Select the object (e.g., Leads, Opportunities) the rule applies to.
  4. Define the Rule Criteria:
    • Example: "Amount > $100,000" triggers the rule.
  5. Specify the Actions:
    • Choose field updates, email alerts, tasks, or outbound messages.
  6. Activate the rule.

Practical Example

  • Scenario: Automatically email a sales manager when an Opportunity with an amount over $50,000 is created.
  • Steps:
    1. Create a workflow rule for the Opportunity object.
    2. Set the criteria: "Amount > $50,000."
    3. Add an email alert action to notify the sales manager.

8.2 Process Builder

Process Builder is a more advanced automation tool than Workflow Rules, offering greater flexibility and functionality.

What Is Process Builder?

  • A visual tool for designing complex workflows with branching logic.
  • Allows multiple criteria and actions in a single process.

Features of Process Builder

  1. Multiple Criteria:

    • Define different conditions and specify separate actions for each.
    • Example: Notify different managers based on the Opportunity's region.
  2. Chained Actions:

    • Trigger additional processes or automation flows.
    • Example: Update an Account field when related Opportunities change.
  3. Cross-Object Updates:

    • Update fields on related objects.
    • Example: Update the "Account Status" when all related Opportunities are closed.
  4. Immediate vs. Scheduled Actions:

    • Immediate: Actions occur as soon as criteria are met.
    • Scheduled: Actions occur at a future time (e.g., send an email 7 days after a contract is signed).

How to Create a Process

  1. Go to Setup and search for Process Builder.
  2. Click New Process and name it.
  3. Select the Object (e.g., Opportunity, Lead) and define the Trigger (e.g., when a record is created or updated).
  4. Add Criteria:
    • Example: "Opportunity Stage = Closed Won."
  5. Define Actions:
    • Example: Update the Account's "Status" to "Active."
  6. Activate the process.

Practical Example

  • Scenario: When a new Opportunity is created with an amount over $100,000, update the related Account's "VIP" field to "Yes."
  • Steps:
    1. Create a Process for the Opportunity object.
    2. Set the criteria: "Amount > $100,000."
    3. Add an action to update the "VIP" field on the related Account.

8.3 Approval Processes

Approval processes are structured workflows that route records to users for approval based on predefined criteria.

What Are Approval Processes?

  • Multi-step workflows that require one or more users to approve or reject records.
  • Often used for contracts, discounts, or budget approvals.

Key Components

  1. Entry Criteria:

    • Defines which records enter the approval process.
    • Example: Opportunities with a discount > 20% require approval.
  2. Approval Steps:

    • Sequential stages in the approval process.
    • Example:
      • Step 1: Manager approves.
      • Step 2: Finance team approves.
  3. Actions:

    • Initial Actions: Performed when a record enters the approval process.
      • Example: Lock the record to prevent changes.
    • Approval Actions: Performed when a record is approved.
      • Example: Send a notification email.
    • Rejection Actions: Performed when a record is rejected.
      • Example: Notify the record owner and unlock the record.

How to Create an Approval Process

  1. Go to Setup and search for Approval Processes.
  2. Click New Approval Process and select the object (e.g., Opportunity, Contract).
  3. Define Entry Criteria:
    • Example: "Discount > 20%."
  4. Configure Approval Steps:
    • Example:
      • Step 1: Manager approval.
      • Step 2: Director approval.
  5. Set up Actions:
    • Initial Action: Lock the record.
    • Approval Action: Notify the sales team.
    • Rejection Action: Unlock the record and notify the owner.
  6. Activate the process.

Practical Example

  • Scenario: Approve discounts above 25% for Opportunities.
  • Steps:
    1. Create an Approval Process for the Opportunity object.
    2. Set the criteria: "Discount > 25%."
    3. Add two steps:
      • Manager approval.
      • Finance approval.
    4. Lock the record when submitted and notify the record owner of the outcome.

Step-by-Step Summary

Workflow Rules

  • Use for simple, single-action automation.
  • Trigger actions like field updates or email alerts.

Process Builder

  • Use for more advanced automation with multiple criteria and actions.
  • Update related records or trigger chained processes.

Approval Processes

  • Use for multi-step approvals requiring sequential or parallel review.
  • Configure criteria, approvers, and actions for approval or rejection.

Key Takeaways for Beginners

  • Workflow Rules: Ideal for straightforward automations.
  • Process Builder: Use for complex workflows with branching logic.
  • Approval Processes: Ensure structured review and approval of records.

Automation (Additional Content)

1. Flow (The Most Powerful Salesforce Automation Tool)

Why is it important?

  • Flow is Salesforce’s most advanced and flexible automation tool, capable of handling complex business processes.
  • It replaces Workflow Rules and Process Builder, offering better scalability and more automation options.
  • Can collect user inputs, create/update/delete records, call external APIs, and manage multi-step approvals.

Types of Flows

Flow Type Description Best Use Cases
Screen Flow User-guided flows that require manual input Data entry wizards, onboarding processes
Record-Triggered Flow Automatically runs when a record is created, updated, or deleted Replace Workflow Rules and Process Builder
Scheduled Flow Runs at a specific time interval Automated data cleanup, customer follow-ups
Autolaunched Flow Runs without user interaction, can be triggered by Apex or other flows Bulk updates, background processing

How to Create a Record-Triggered Flow

  1. Navigate to Setup → Search for Flow.
  2. Click New Flow → Select Record-Triggered Flow.
  3. Choose the Object to trigger the Flow (e.g., Opportunity).
  4. Define Trigger Conditions (e.g., "Stage = Closed Won").
  5. Add Actions, such as:
  • Create a Task (e.g., “Send Thank You Email”).
  • Update a Record (e.g., Mark Account as "VIP").
  1. Save and Activate the Flow.

Example Scenario

  • When a Lead is converted, the Flow:
    • Creates a follow-up task for the Sales Rep.
    • Sends a welcome email to the new Contact.
    • Notifies the Sales Manager via Chatter.

2. Einstein Next Best Action (AI-Driven Automation for Smarter Decision-Making)

Why is it important?

  • Einstein Next Best Action (NBA) combines AI and business automation to recommend the best action for sales, service, and marketing teams.
  • Provides real-time suggestions to improve efficiency and customer experience.

Use Cases

Scenario Einstein Recommendation
Sales Team Suggests which Opportunity is most likely to close
Customer Support Recommends offering a refund, discount, or product upgrade based on customer history
Approval Process Dynamically suggests fast-tracking high-value deals

Example Scenario

  • In the Case Management page, Einstein suggests:
    • If a customer has logged more than 3 complaints, offer a free upgrade.
    • If a customer meets a promotional requirement, automatically apply a 10% discount.

3. Approval Process with Dynamic Approver Selection

Why is it important?

  • Dynamic Approval Processes allow the system to choose the approver based on record values, rather than using a static approver list.
  • Useful for multi-level approvals, region-specific workflows, and departmental approvals.

How to Configure a Dynamic Approval Process

  1. Navigate to Setup → Search for Approval Processes.
  2. Click New Approval Process and select an Object (e.g., Opportunities).
  3. Set up Entry Criteria (e.g., "Amount > $100,000").
  4. Choose Next Approver Determined By Field.
  5. Select a field that stores the approver’s name (e.g., Regional Manager, Finance Director).
  6. Activate the Approval Process.

Example Scenario

  • If an Opportunity is over $100,000, it is sent to the CFO for approval.
  • If under $100,000, it goes to the Sales Manager.

4. Automated Scheduled Jobs (Recurring Automation for Data Maintenance)

Why is it important?

  • Scheduled Jobs allow Salesforce to automatically run tasks at specific intervals, reducing manual work.
  • Useful for data cleanup, follow-ups, and periodic report generation.

How to Create a Scheduled Flow

  1. Navigate to Setup → Search for Flow.
  2. Click New Flow → Select Scheduled Flow.
  3. Set Trigger Time (e.g., Run daily at 12 AM).
  4. Define Automation Actions, such as:
  • Delete old records (e.g., Leads inactive for 6+ months).
  • Send reminder emails (e.g., Notify sales reps about overdue follow-ups).
  1. Save and Activate the Flow.

Example Scenario

  • Every month, Salesforce:
    • Checks all Leads with no activity for 30+ days.
    • Automatically sends a follow-up email.
    • If no response after 7 days, assigns the Lead to a new sales rep.

Final Summary

Feature Description Best Use Cases
Flow Automates complex business processes Lead conversion automation, customer onboarding
Einstein Next Best Action AI-driven recommendations for optimal decision-making Suggesting discounts, service upgrades, priority leads
Dynamic Approval Process Assigns approvers dynamically based on record values Region-specific approvals, multi-step workflows
Scheduled Jobs Runs automation on a recurring schedule Data cleanup, follow-up reminders, recurring reports

Frequently Asked Questions

What is Salesforce Flow?

Answer:

Salesforce Flow is the platform’s primary declarative automation tool for building business processes.

Explanation:

Flow allows administrators to automate actions such as updating records, sending notifications, creating related records, guiding users through screens, and applying logic based on conditions. It has become the main automation framework for Salesforce admins, replacing many older declarative tools in practical use. The exam often tests whether candidates recognize Flow as the preferred automation solution for modern orgs. One reason Flow is so important is flexibility: it supports screen flows, record-triggered flows, scheduled flows, and more. A good rule of thumb is that if the requirement involves structured automation without code, Flow is usually the most likely answer. Administrators should understand both what Flow can do and when it is preferable to simpler point features.

Demand Score: 95

Exam Relevance Score: 96

When should an administrator use a record-triggered flow?

Answer:

Use a record-triggered flow when automation should run automatically after a record is created, updated, or deleted.

Explanation:

Record-triggered flows are used when the automation depends on changes to Salesforce data. For example, when an Opportunity is marked Closed Won, a flow can create a follow-up task, update related records, or send a notification. This type of flow is especially important because many traditional automation use cases now belong here. On the exam, the clue is usually an automatic business process tied directly to record changes. Administrators should also know that record-triggered flows can run before save or after save, depending on the need. Before-save flows are optimized for updating the same record, while after-save flows are better for actions involving related records, notifications, or more complex processing.

Demand Score: 91

Exam Relevance Score: 95

What is the difference between a before-save flow and an after-save flow?

Answer:

A before-save flow updates the triggering record efficiently before it is saved, while an after-save flow runs after the save and supports broader actions.

Explanation:

Before-save flows are typically used for fast field updates on the same record. They are efficient because the changes occur before the database commit finishes. After-save flows are used when the automation needs to create related records, send emails, post notifications, or update other records. The exam often tests this distinction by giving a requirement and asking for the best automation design. If the task is only to modify fields on the record being saved, before-save is usually best. If the task affects other records or downstream actions, after-save is usually required. Understanding this difference helps administrators design flows that are both correct and performant.

Demand Score: 86

Exam Relevance Score: 93

Why is Flow preferred over older tools like Workflow Rules or Process Builder?

Answer:

Because Flow is more flexible, more capable, and serves as Salesforce’s strategic automation platform.

Explanation:

Older tools such as Workflow Rules and Process Builder were useful for simpler automation, but they are limited compared with Flow. Flow supports richer logic, more action types, better control over execution, and broader use cases such as screens, scheduled automation, and advanced record processing. Salesforce guidance has increasingly centered on Flow as the modern declarative standard, so exam candidates should be comfortable treating it as the primary answer in most automation scenarios. A common mistake is selecting Workflow Rules for cases that now belong more naturally to Flow. When the requirement involves branching logic, multiple actions, record creation, or scalable admin design, Flow is usually the stronger answer.

Demand Score: 84

Exam Relevance Score: 92

What is a screen flow used for?

Answer:

A screen flow is used to guide users through interactive steps where they enter data or make choices.

Explanation:

Unlike background automation, a screen flow displays screens to the user and collects input during execution. It is useful for guided processes such as intake forms, step-by-step service procedures, qualification wizards, or internal approval intake. Screen flows can simplify complex processes by reducing user confusion and ensuring required information is captured in the right order. On the exam, screen flow is often the best answer when the requirement includes user interaction during the automation itself. If the process should happen invisibly after a record change, another type of flow is more appropriate. The key clue is whether a human must interact with the process as it runs.

Demand Score: 79

Exam Relevance Score: 88

What is a common best practice for Salesforce automation design?

Answer:

Keep automation as simple, clear, and consolidated as possible to reduce errors and maintenance problems.

Explanation:

As Salesforce orgs grow, automation can become difficult to manage if too many rules, flows, and overlapping conditions are created without structure. Good admin practice is to avoid unnecessary duplication, use clear naming conventions, document intent, and design flows that are easy to troubleshoot. On the exam, this often appears as a question about reducing complexity or preventing conflicting automation. Consolidation matters because multiple overlapping automations can create unexpected updates, recursion, or performance issues. The best answer is usually the one that simplifies the design while still meeting the requirement. Administrators are not just expected to automate processes; they are expected to do so in a maintainable and scalable way.

Demand Score: 82

Exam Relevance Score: 89

ADM-201 Training Course