Question

Difficulty: MediumFlow Types and Triggers

An administrator is designing an automation strategy for a custom object named Facility_Work_Order__c. The business process requires two distinct automated actions:

1. When a record is created or updated, automatically calculate and set the Priority field on the work order prior to committing the record to the database.
2. When a work order is marked as 'Closed', automatically create a related Billing_Invoice__c record and dispatch an email alert to the department supervisor.

Which two Flow configurations should the administrator select to fulfill these requirements efficiently? (Choose two.)

  1. A Record-Triggered Flow configured for 'Fast Field Updates' (before-save) to update the Priority field on the triggering record.Answer
  2. A Record-Triggered Flow configured for 'Actions and Related Records' (after-save) to create the related Billing_Invoice__c record and send the email alert.Answer
  3. C
    A Record-Triggered Flow configured for 'Actions and Related Records' (after-save) to update the Priority field on the triggering record.
  4. D
    A Record-Triggered Flow executing DML Create and Update elements inside a loop before system validation rules evaluate.

Answer

Configure a Record-Triggered Flow set to 'Fast Field Updates' for updating fields on the triggering record, and configure a Record-Triggered Flow set to 'Actions and Related Records' for creating the related record and sending the email alert.
Updating fields on the triggering record prior to commit is best achieved using a Record-Triggered Flow optimized for Fast Field Updates (before-save). Creating related records and firing outbound actions such as email alerts require an after-save Record-Triggered Flow configured for Actions and Related Records.

Step-by-Step Solution

1
Analyze the first requirement: updating fields directly on the triggering Facility_Work_Order__c record prior to database commit.
Identify that 'Fast Field Updates' (before-save record-triggered flow) updates the triggering record in memory before the database save operation, providing the best performance.
Before-save flows do not require an explicit Update Records element or additional DML transactions for same-record updates.
2
Analyze the second requirement: creating a related record (Billing_Invoice__c) and sending an email alert upon record closure.
Identify that 'Actions and Related Records' (after-save record-triggered flow) is necessary.
Creating records on other objects and sending external communications/alerts require the triggering record to be saved to the database first.
3
Select the two flow trigger types matching the requirements.
Choose Fast Field Updates for same-record updates and Actions and Related Records for related record operations and alerts.
This combination adheres to Salesforce architectural best practices for record-triggered automations.

Key Concept

Selecting between Fast Field Updates (Before-Save) and Actions and Related Records (After-Save) in Record-Triggered Flows
Estimated Time:1m 30s
Rate this question