An operations team at an electronics distributor requires automated logic on the custom object Customer_Return__c. When a return record is submitted, the system must immediately set the Inspection_Status__c field on the triggering return record prior to committing it to the database. Additionally, the process must update the In_Stock_Quantity__c field on the parent Inventory_Item__c record and trigger an outbound email alert. Which two Flow trigger and optimization configurations should the administrator implement to satisfy these business requirements? (Choose two.)
- A Record-Triggered Flow optimized for Fast Field Updates to update the Inspection_Status__c field on the triggering return record.Answer
- A Record-Triggered Flow optimized for Actions and Related Records to update the parent Inventory_Item__c record and execute the email alert.Answer
- CA Record-Triggered Flow optimized for Fast Field Updates to update the parent Inventory_Item__c record and send the email alert.
- DA Schedule-Triggered Flow running at daily intervals to evaluate new returns, populate the inspection status, and dispatch email alerts.
Answer
The administrator should configure a Record-Triggered Flow optimized for Fast Field Updates to update the triggering return record's status field, and a Record-Triggered Flow optimized for Actions and Related Records to update the parent inventory item and send the email alert.
Salesforce provides two primary optimization settings for record-triggered flows. Fast Field Updates (before-save) execute before the triggering record is saved to the database, making them ideal for updating fields on the triggering record with optimal performance. In contrast, Actions and Related Records (after-save) execute after the record has been committed to the database, which is required when creating or updating related records or executing external actions such as sending email alerts.
Step-by-Step Solution
Key Concept
Record-Triggered Flow trigger optimization: Fast Field Updates (before-save) versus Actions and Related Records (after-save)
Estimated Time:1m 15s