Record-Triggered Flows are a powerful automation tool in Salesforce that execute when a record is created, updated, or deleted. They replace the older Workflow Rules and Process Builder, offering more flexibility and functionality within a single automation framework.
Record-Triggered Flows activa…Record-Triggered Flows are a powerful automation tool in Salesforce that execute when a record is created, updated, or deleted. They replace the older Workflow Rules and Process Builder, offering more flexibility and functionality within a single automation framework.
Record-Triggered Flows activate based on specific record changes in your Salesforce org. You can configure them to run when a record is created, when a record is updated, when a record is created or updated, or when a record is deleted.
There are three optimization options for Record-Triggered Flows:
1. Fast Field Updates: Runs before the record is saved to the database, allowing you to update fields on the triggering record efficiently.
2. Actions and Related Records: Runs after the record is saved, enabling you to update related records, send emails, create tasks, and perform other actions.
3. Scheduled Paths: Allows you to schedule actions to run at a specific time after the triggering event, such as sending a follow-up email three days after a case is created.
Key components of Record-Triggered Flows include Entry Conditions that determine which records trigger the flow, Decision Elements for branching logic, and various Action elements like Create Records, Update Records, Delete Records, and Send Email.
Best practices for Record-Triggered Flows include bulkifying your flows to handle multiple records efficiently, avoiding recursive loops by using entry conditions carefully, and consolidating multiple automations on the same object into a single flow when possible.
Record-Triggered Flows are part of Salesforce Flow Builder and represent the recommended approach for record-based automation. They provide a visual interface for building complex business logic and can handle scenarios that previously required multiple automation tools or custom Apex code. Administrators should understand flow types, optimization settings, and debugging techniques to effectively implement and troubleshoot these automations.
Record-Triggered Flows: Complete Guide for Salesforce Administrator Exam
Why Record-Triggered Flows Are Important
Record-Triggered Flows are a cornerstone of Salesforce automation and represent the modern, declarative approach to automating business processes. As Salesforce phases out Workflow Rules and Process Builder, Record-Triggered Flows have become the primary automation tool that administrators must master. Understanding this concept is essential for both the certification exam and real-world Salesforce administration.
What Are Record-Triggered Flows?
Record-Triggered Flows are automated processes that execute when a record is created, updated, or deleted in Salesforce. They are built using Flow Builder and allow administrators to perform complex automation tasks such as:
• Creating, updating, or deleting records • Sending emails and notifications • Calling Apex code • Posting to Chatter • Making outbound calls to external systems
How Record-Triggered Flows Work
Trigger Types: Record-Triggered Flows can be configured to run when: • A record is created - Executes only when new records are inserted • A record is updated - Executes when existing records are modified • A record is created or updated - Executes in both scenarios • A record is deleted - Executes when records are removed
Execution Timing (Run Options): • Before Save - Runs before the record is saved to the database. Best for updating fields on the same record that triggered the flow. Does not require a DML operation. • After Save - Runs after the record is committed to the database. Required when you need to access the record ID, create related records, or perform actions that need the record to exist first. • Scheduled Paths (Asynchronous) - Runs at a specified time after the trigger event, useful for follow-up actions like reminder emails.
Entry Conditions: You can specify conditions that must be met for the flow to execute, including: • Run every time conditions are met • Run only when specified conditions change from false to true
Order of Execution Context
Understanding where Record-Triggered Flows fit in the order of execution is crucial: 1. System validation rules 2. Before-save flows 3. Custom validation rules 4. Duplicate rules 5. Record saved to database (not committed) 6. After-save flows 7. Assignment rules, escalation rules 8. Record committed to database 9. Post-commit logic
Best Practices
• Use Before Save flows when updating fields on the triggering record for better performance • Bulkify your flows by avoiding loops that perform DML operations • Limit the number of flows per object to reduce complexity • Use entry conditions to prevent unnecessary flow executions • Document your flows with descriptions and element labels
Exam Tips: Answering Questions on Record-Triggered Flows
Key Concepts to Remember:
1. Before vs. After Save: Know when to use each. Before Save is more efficient for field updates on the same record. After Save is necessary when you need the record ID or need to create related records.
2. Entry Conditions: Understand the difference between running every time conditions are met versus only when conditions change from false to true. The latter prevents the flow from re-running on subsequent edits.
3. Scheduled Paths: These require After Save configuration and are used for time-based actions like sending follow-up emails after a certain period.
4. Performance Considerations: Questions may ask about the most efficient approach. Before Save flows that update the triggering record do not consume DML limits.
5. Delete Triggers: Remember that delete-triggered flows can only run After Save.
Common Exam Scenarios:
• A scenario requiring a field update on the same record - Answer: Before Save flow • A scenario requiring creation of a related record - Answer: After Save flow • A scenario requiring an action X days after record creation - Answer: Scheduled Path • A scenario where automation should only run once when criteria first becomes true - Answer: Entry condition set to run only when conditions change from false to true
Watch For:
• Questions that mix terminology from Workflow Rules and Process Builder with Flow terminology • Scenarios that test your understanding of the order of execution • Questions about recursion and how to prevent infinite loops • Scenarios comparing declarative solutions (flows) versus programmatic solutions (Apex triggers)