An administrator is designing automation for a custom object named Patient_Intake__c. The administrator wants to use Fast Field Updates (before-save) record-triggered flows wherever possible to maximize performance. Which two requirements can be fulfilled using a Fast Field Updates record-triggered flow? (Choose 2)
- Setting a calculated triage category field on the triggering Patient_Intake__c record prior to database commitCevap
- Populating a default clinic region on the triggering Patient_Intake__c record using values retrieved from the related Account recordCevap
- CCreating a new Follow_Up_Task__c record linked to the intake record when the intake status changes
- DSending an automated email alert notification to the attending physician upon record submission
Cevap
Setting a calculated triage category field on the triggering record prior to database commit, and populating a default clinic region on the triggering record using values retrieved from the related Account record.
Fast Field Updates (before-save) record-triggered flows are optimized specifically for updating field values on the triggering record before the record is saved to the database. They can evaluate formulas, navigate relationships to read related record fields, and update the triggering record without incurring additional DML operations.
Adım Adım Çözüm
Anahtar Kavram
Fast Field Updates (Before-Save) vs Actions and Related Records (After-Save) Record-Triggered Flows
Tahmini Süre:1m 30s