A Salesforce Administrator needs to automate a process for a custom object named Event Sponsorship. When an Event Sponsorship record's status is changed to 'Confirmed', the system must satisfy two requirements: (1) update a custom field named Discount_Rate__c on the triggering record prior to saving, and (2) create a related Task record assigned to the finance team. Which TWO automation approaches should the administrator combine to meet these requirements efficiently while adhering to Salesforce best practices? (Select TWO answers.)
- Use a Record-Triggered Flow set to Fast Field Updates (before-save) to update the Discount_Rate__c field on the triggering Event Sponsorship record.Cevap
- Use a Record-Triggered Flow set to Actions and Related Records (after-save) to create the related Task record for the finance team.Cevap
- CUse a single Record-Triggered Flow set to Actions and Related Records (after-save) to perform both the same-record field update and the related Task record creation.
- DCreate a Roll-Up Summary field on the parent Account object linked via a lookup relationship to calculate and push the discount value back to the Event Sponsorship record.
Cevap
The administrator should use a Record-Triggered Flow configured for Fast Field Updates (before-save) to perform the same-record update on Discount_Rate__c, and a Record-Triggered Flow configured for Actions and Related Records (after-save) to create the related Task record.
Salesforce best practice mandates using a Fast Field Updates (before-save) Record-Triggered Flow when updating fields on the record that triggered the flow, as it performs updates significantly faster without extra DML steps. An Actions and Related Records (after-save) Record-Triggered Flow is appropriate for creating child or related records like Tasks because those require access to record IDs and relationship execution after the primary record save completes.
Adım Adım Çözüm
Anahtar Kavram
Selecting optimal record-triggered flow optimization types (Before-Save vs. After-Save) based on record update context and related object operations.