7. Automation

Automated process triggered when specific criteria are met on a single record, executing immediate or time-dependent actions.

Actions triggered by a Workflow Rule, occurring immediately or after a specified time.

A process automation tool used to define the steps required to approve a record.

The initial criteria a record must meet to start the Approval process.

Actions performed immediately after a record is submitted for approval.

Steps within an Approval Process where a decision to approve or reject is made.

Actions performed upon final approval or rejection of a record.

Records within an approval process are locked, preventing changes while the process is ongoing.

A type of Flow that provides a user interface for gathering or displaying information.

A branching path in a Flow that handles errors.

A Flow element that undoes all database changes made up to a point in a Screen Flow.

A grouping of one or more criteria with actions that can automatically fire based off of the evaluation of the criteria.

A Flow that performs automated tasks when a record is created, updated, or deleted.

System-provided variables that give information about the Salesforce org, the running user, and more.

A Flow Element that launches another Flow.

The order in which processes fire in the background when a record is saved or updated in Salesforce.

An automated process initiated through a button or flow, enabling multiple approval steps with a maximum of 30 steps and 25 approvers per step.

Allows for record editing by approvers or admins during the approval process, providing flexibility.

A visual tool for creating automated processes with point-and-click functionalities, offering more power than workflow rules.

Types of processes in Process Builder, encompassing record change, platform events, and invocable operations.

The actions a Process Builder can perform, including Apex execution, record manipulation, email sending, and flow launching.

Different types of Flows based on their trigger and functionality, categorized as Record-triggered, Autolaunched, Platform Event, Scheduled, and Screen.

The data containers used by Flow elements, including variables, constants, formulas, and explicit/implicit resources.

The building blocks of a Flow, encompassing components like screens, actions, decisions, loops, and record operations.

Components within Screen Flows that enable data input and output, creating interactive elements for users.

The ability to directly assign values to Flow resources using specific components, simplifying data management.

Flows that are executed when a specific Platform Event is published, allowing for trigger-based automation.

An automation tool that triggers pre-defined Workflow Actions when a single record meets specific criteria.

A type of Flow that runs in the background whenever a predetermined Platform Event is published.

Customizable event notifications that follow a publisher/subscriber model. Events can be triggered both inside and outside of Salesforce.

Flows without an associated trigger, commonly used for reusable logic within other Flows.

Flows that execute at a specific time and frequency (once, daily, or weekly).

Tools for testing and troubleshooting flows, including running flows as other users, detailed debug logs, and rollback options.

A branching path that executes when a Flow error occurs.

Important for keeping flows organized and understandable.

Avoid placing database operations (create, update, get) inside of loops.

When working with multiple records, always use collections and operate on the entire collection instead of handling individual records within a loop.

Salesforce is shifting away from Workflow Rules and Process Builder, with Flows being the primary automation tool.

Flows offer a wide range of automation options and capabilities that span across other Salesforce tools.

Understanding the context in which a Flow executes (user context vs. system context, or before/after save) is crucial for success.

Thorough testing using debugging tools and adhering to best practices is essential for building stable and efficient Flows.

Understanding the sequence in which Salesforce processes different elements is crucial for complex Flows, particularly Record-Triggered Flows.

Creating a Task record, sending an email alert, and making field updates on a record.

This setting in Workflow Rules means the rule will be evaluated when a record is initially created and every time it's edited, as long as the updated record meets the specified criteria.

A comprehensive automation tool in Salesforce that uses a set of actions (Elements) to execute logic based on defined criteria. Each execution is called a Flow Interview.

Auto-launched Flows trigger automatically when a predefined event happens. They are not initiated by user actions.

A customizable event notification that can be sent from inside or outside a Salesforce organization, and does not require a database change.

The Rollback Records element in Screen Flows helps to undo changes made during the flow. If an error occurs or a user cancels, it restores the original state of the record.

In Approval Processes, the Submit for Approval button is the trigger that starts the approval process. Users click it on the record’s page to send it for review and approval.

Approval processes allow you to automate actions like sending an email notification, updating record fields, and triggering a next step (approver) in the process.

Record-Triggered Flows are designed for a specific record, whereas Platform Event Triggered Flows are triggered by events that can happen outside of a record's scope.

In Record-Triggered Flows, the '$Record' global variable accesses the triggering record's information, while the '$Record__Prior' global variable provides access to the record's previous state before the change.