Examkin

Soru

Zorluk: Çok zorFlow Types and Triggers

Cloud Kicks needs to automate business logic for custom Warranty Claim records. When a claim is created or modified, two specific technical requirements must be satisfied:

1. Calculate an internal risk score and set the claim status on the triggering record prior to committing it to the database, without issuing additional DML statements or re-triggering object execution rules.
2. Create a related audit record and transmit an outbound email notification to an external vendor after the claim record has been successfully committed to the database.

Which two flow trigger configurations should the administrator combine to meet these requirements efficiently?

  1. A Fast Field Updates (Before-Save) Record-Triggered Flow to set the risk score and claim status directly on the triggering record before database commit.Cevap
  2. An Actions and Related Records (After-Save) Record-Triggered Flow to create the related audit record and send the email notification.Cevap
  3. C
    An Actions and Related Records (After-Save) Record-Triggered Flow that uses an explicit Update Records element to modify fields on the triggering record before save.
  4. D
    A Schedule-Triggered Flow running every 15 minutes that queries new claims, updates fields in a loop, and creates related records.

Cevap

The administrator should implement a combination of a Fast Field Updates (Before-Save) Record-Triggered Flow to update the triggering record before commit, and an Actions and Related Records (After-Save) Record-Triggered Flow to generate related records and execute outbound actions after commit.
The scenario presents two distinct operational requirements: modifying fields on the triggering record before saving to the database, and performing post-commit record creation and external messaging. A Fast Field Updates (Before-Save) flow handles same-record field modifications in memory without DML overhead. An Actions and Related Records (After-Save) flow ensures that child audit records are created and outbound emails are sent only after the primary record has successfully passed database commit.

Adım Adım Çözüm

1
Evaluate the requirement for same-record field updates before database commit.
Determine that updating fields on the record that launched the flow prior to saving requires a Fast Field Updates (Before-Save) Record-Triggered Flow.
Before-save flows run up to 10 times faster than after-save flows because values are assigned directly to the memory buffer without requiring explicit DML operations or re-triggering the order of execution.
2
Evaluate the requirement for creating child records and executing post-save communications.
Determine that creating related audit logs and sending external emails requires an Actions and Related Records (After-Save) Record-Triggered Flow.
Post-commit operations, such as creating records on other objects or notifying external services, must take place after the primary record has successfully passed system validation rules and database save.

Anahtar Kavram

Record-Triggered Flow Optimization: Before-Save vs. After-Save Triggers
Bu soruyu puanla

Konular

Flow Types and Triggers

Bu konudan daha fazla soru