A Salesforce administrator is tasked with updating the custom field Risk_Score__c on the Case object whenever a Case record is created or modified, prior to saving the record to the Salesforce database. The calculation depends solely on field values within the triggering Case record itself, without requiring changes to related records or external web service callouts. Which flow implementation option provides the most efficient and recommended approach?
- Configure a Record-Triggered Flow optimized for Fast Field Updates (Before-Save).Cevap
- BConfigure a Record-Triggered Flow optimized for Actions and Related Records (After-Save).
- CConfigure a Schedule-Triggered Flow that runs nightly to update the field on modified Case records.
- DConfigure an Autolaunched Flow invoked by a Process Builder process upon Case creation or update.
Cevap
Configure a Record-Triggered Flow optimized for Fast Field Updates (Before-Save).
Configuring a Record-Triggered Flow optimized for Fast Field Updates (Before-Save) is the recommended best practice when updating values on the triggering record prior to database commit. Before-Save flows update the record values in memory before saving to the database, offering optimal execution speed and avoiding additional DML operations or re-triggering validation rules.
Adım Adım Çözüm
Anahtar Kavram
Fast Field Updates vs Actions and Related Records in Record-Triggered Flows