Soru

Zorluk: OrtaFlow Types and Triggers

An administrator at a manufacturing company is designing an automation strategy for a custom object named Maintenance_Ticket__c. The business requires two automated operations:

1. Automatically calculate and populate a Routing_Code__c field on the triggering Maintenance_Ticket__c record before it is committed to the database.
2. Automatically create a child Task record assigned to the operations manager whenever a Maintenance_Ticket__c record is updated with a Severity__c of 'Critical'.

Which two flow configurations should the administrator select to fulfill these requirements efficiently? (Choose two.)

  1. A Record-Triggered Flow configured for Fast Field Updates to populate the routing code on the maintenance ticketCevap
  2. A Record-Triggered Flow configured for Actions and Related Records to create the follow-up task recordCevap
  3. C
    A Record-Triggered Flow configured for Fast Field Updates to create the child task record
  4. D
    A Record-Triggered Flow configured for Actions and Related Records to perform the same-record routing code assignment

Cevap

Use a Record-Triggered Flow configured for Fast Field Updates to set the routing code on the triggering maintenance ticket, and a Record-Triggered Flow configured for Actions and Related Records to create the child task record.
Salesforce provides two primary optimization paths for record-triggered flows. Fast Field Updates (before-save) execute prior to database commit and are best practice for updating fields directly on the triggering record without extra DML statements. Actions and Related Records (after-save) execute after the record has been saved, enabling the creation and modification of related records, such as child Tasks, as well as executing external actions.

Adım Adım Çözüm

1
Analyze the requirement for updating fields on the triggering record before database commit
Identified the need for a before-save Record-Triggered Flow (Fast Field Updates).
Fast Field Updates execute before the record is written to the database, allowing immediate field updates on $Record without extra DML operations or re-triggering the full save cycle.
2
Analyze the requirement for creating a separate related record (Task)
Identified the need for an after-save Record-Triggered Flow (Actions and Related Records).
Creating related records requires the triggering record to have an active ID and database commit context, which is only supported in after-save flows.
3
Select the two flow configurations that align directly with each requirement
Selected Fast Field Updates for same-record field population and Actions and Related Records for related task creation.
This combination adheres to Salesforce best practices for performance and trigger optimization.

Anahtar Kavram

Record-Triggered Flow Optimization: Fast Field Updates (Before-Save) vs. Actions and Related Records (After-Save)
Bu soruyu puanla