An administrator at a manufacturing company is designing an automation strategy for a custom object named Maintenance_Ticket__c. The business requires two automated operations:
1. Automatically calculate and populate a Routing_Code__c field on the triggering Maintenance_Ticket__c record before it is committed to the database.
2. Automatically create a child Task record assigned to the operations manager whenever a Maintenance_Ticket__c record is updated with a Severity__c of 'Critical'.
Which two flow configurations should the administrator select to fulfill these requirements efficiently? (Choose two.)
- A Record-Triggered Flow configured for Fast Field Updates to populate the routing code on the maintenance ticketAnswer
- A Record-Triggered Flow configured for Actions and Related Records to create the follow-up task recordAnswer
- CA Record-Triggered Flow configured for Fast Field Updates to create the child task record
- DA Record-Triggered Flow configured for Actions and Related Records to perform the same-record routing code assignment
Answer
Use a Record-Triggered Flow configured for Fast Field Updates to set the routing code on the triggering maintenance ticket, and a Record-Triggered Flow configured for Actions and Related Records to create the child task record.
Salesforce provides two primary optimization paths for record-triggered flows. Fast Field Updates (before-save) execute prior to database commit and are best practice for updating fields directly on the triggering record without extra DML statements. Actions and Related Records (after-save) execute after the record has been saved, enabling the creation and modification of related records, such as child Tasks, as well as executing external actions.
Step-by-Step Solution
Key Concept
Record-Triggered Flow Optimization: Fast Field Updates (Before-Save) vs. Actions and Related Records (After-Save)