Soru

Zorluk: OrtaFlow Types and Triggers

A business process requires that whenever an Order record's Status is changed to 'Activated', the system must automatically create a new Shipment record linked to that Order and send an email notification to the warehouse supervisor. Which flow type and trigger configuration should the administrator select to fulfill these requirements?

  1. A
    Record-Triggered Flow configured for Fast Field Updates (before the record is saved)
  2. Record-Triggered Flow configured for Actions and Related Records (after the record is saved)Cevap
  3. C
    Schedule-Triggered Flow configured to run hourly to check for activated orders
  4. D
    Autolaunched Flow with no trigger invoked directly by database commit events

Cevap

Record-Triggered Flow configured for Actions and Related Records (after the record is saved)
A Record-Triggered Flow configured for Actions and Related Records executes after the triggering record has been written to the database. This after-save context provides access to the record ID and supports creating related records (such as Shipment records) and executing external actions (such as sending email alerts).

Adım Adım Çözüm

1
Analyze the automation requirements and actions needed
Identified the need to create a related Shipment record and send an email notification when an Order record is updated.
Creating related records and sending emails are external/DML operations that cannot be performed in before-save triggers.
2
Evaluate the trigger mechanism and execution timing
A record-triggered event on Order update is needed, specifically after the record is saved to access the record ID and create related records.
Before-save flows (Fast Field Updates) only permit field value assignments on the triggering record itself.
3
Select the appropriate Flow Type and Trigger configuration
Choose a Record-Triggered Flow optimized for Actions and Related Records.
This configuration allows record creation and core actions upon database commit.

Anahtar Kavram

Selecting between Fast Field Updates (before-save) and Actions and Related Records (after-save) in Record-Triggered Flows
Bu soruyu puanla