An administrator is evaluating automation design requirements for the custom object Equipment_Audit__c to optimize transaction processing speed and minimize system overhead. Which two use cases should be implemented using a Record-Triggered Flow configured for Fast Field Updates (Before-Save)? (Choose 2)
- Updating fields on the triggering Equipment_Audit__c record prior to it being committed to the database.Cevap
- Evaluating parent Account record attributes to populate default field values on the triggering Equipment_Audit__c record before save.Cevap
- CCreating a follow-up Task record assigned to the auditor whenever an Equipment_Audit__c record is marked as Non-Compliant.
- DPublishing a custom Platform Event to notify an external service after the Equipment_Audit__c record status changes.
Cevap
Updating fields on the triggering Equipment_Audit__c record prior to database commit, and evaluating parent Account record attributes to populate default field values on the triggering Equipment_Audit__c record before save.
Fast Field Updates (before-save flows) execute prior to the record being saved to the database. They are optimized specifically for updating fields on the record that triggered the flow. Reading related record fields to set values on the triggering record before database write is fully supported in before-save flows without triggering additional system save cycles.
Adım Adım Çözüm
Anahtar Kavram
Fast Field Updates vs Actions and Related Records Trigger Types