Question

Difficulty: MediumFlow Types and Triggers

A logistics company manages transport assets using a custom object named Fleet_Vehicle__c. When an operator updates a vehicle record and marks the Service_Completed__c checkbox as true, the system must immediately populate the Next_Inspection_Date__c and set the Status__c field to 'Ready for Dispatch'. No external web services, email alerts, or related object records need to be updated. Which flow type and trigger configuration provides the most efficient solution for this requirement?

  1. A
    A Record-Triggered Flow configured for Actions and Related Records that executes after the record is saved, utilizing an Update Records element to modify the vehicle fields.
  2. A Record-Triggered Flow configured for Fast Field Updates that updates fields on the triggering Fleet_Vehicle__c record before it is saved to the database.Answer
  3. C
    An Autolaunched Flow that iterates over vehicle records in a loop and performs an Update Records operation within each iteration.
  4. D
    A Record-Triggered Flow configured after-save that relies on standard validation rules executing after the flow to verify updated field values.

Answer

A Record-Triggered Flow configured for Fast Field Updates that updates fields on the triggering Fleet_Vehicle__c record before it is saved to the database.
A Record-Triggered Flow configured for Fast Field Updates (before-save) runs before the record is saved to the database. It updates fields directly on the $Record global variable in memory, running up to 10 times faster than after-save flows and eliminating the need for an explicit Update Records element or additional DML transactions.

Step-by-Step Solution

1
Analyze the automation requirement and target object.
The requirement specifies modifying fields strictly on the triggering Fleet_Vehicle__c record upon an update, with no external actions or related records involved.
Identifying the target of the update dictates whether a before-save (Fast Field Updates) or after-save (Actions and Related Records) flow is optimal.
2
Evaluate flow trigger timing and optimization capabilities.
Fast Field Updates (before-save record-triggered flows) run before the record is committed to the database and update $Record values in memory without issuing separate DML statements.
Salesforce best practices dictate using Fast Field Updates for same-record field modifications to maximize transaction performance and prevent extra save cycles.
3
Select the correct configuration option.
A before-save record-triggered flow configured for Fast Field Updates meets all requirements efficiently.
This configuration avoids unnecessary DML overhead and prevents redundant trigger/validation executions.

Key Concept

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