Examkin

Soru

Zorluk: OrtaFlow Types and Triggers

An organization is configuring business process automation for a custom object named Solar_Installation__c. The administrator must fulfill two specific operational requirements:

1. Automatically calculate and populate Estimated_Completion_Date__c and System_Capacity__c on the triggering record prior to saving the record into the database.
2. When an installation status reaches "Ready for Inspection", immediately send an automated email alert to the regional inspector and create a follow-up Task for the site supervisor.

Which two flow configurations should the administrator implement to fulfill these requirements following Salesforce best practices? (Choose two.)

  1. A Record-Triggered Flow configured for Fast Field Updates (before the record is saved) to populate the fields on the triggering record without additional DML operations.Cevap
  2. A Record-Triggered Flow configured for Actions and Related Records (after the record is saved) to execute the email alert and generate the task.Cevap
  3. C
    A Record-Triggered Flow configured for Actions and Related Records that uses an Update Records element to modify the triggering record's date and capacity fields.
  4. D
    A Schedule-Triggered Flow that evaluates all Solar_Installation__c records hourly to check for status changes and fire inspector notifications.

Cevap

Configure a Record-Triggered Flow with Fast Field Updates for same-record field calculations and a Record-Triggered Flow with Actions and Related Records for notifications and task creation.
Salesforce architecture mandates using Fast Field Updates (before-save flows) whenever updates are restricted to the record that triggered the flow. This updates the field values in memory without issuing a separate DML statement. Conversely, Actions and Related Records (after-save flows) are required when an automated process must create or update related records (such as Tasks) or execute external actions (such as email alerts), because the parent record must be committed to the database with a valid ID first.

Adım Adım Çözüm

1
Evaluate requirement 1 regarding populating fields on the triggering record before database commit.
Identify that updating fields on the triggering record prior to save is best handled by a Record-Triggered Flow optimized for Fast Field Updates (Before-Save).
Fast Field Updates update the $Record variable directly in memory before commit, eliminating additional DML operations and avoiding trigger re-entry.
2
Evaluate requirement 2 regarding sending email alerts and creating child Task records.
Identify that executing external actions and creating related records requires a Record-Triggered Flow optimized for Actions and Related Records (After-Save).
Before-save flows cannot perform external actions or create related records; these operations require the record to have an ID committed in the database.
3
Identify the incorrect configurations.
Eliminate the after-save flow for same-record updates and the hourly scheduled flow for immediate notification requirements.
Updating the same record in an after-save flow introduces performance overhead, while scheduled flows introduce latency and fail the real-time requirement.

Anahtar Kavram

Selecting appropriate Flow triggers and optimization modes (Fast Field Updates vs. Actions and Related Records) based on operational scope and Salesforce execution order best practices.
Tahmini Süre:1m 30s
Bu soruyu puanla

Konular

Flow Types and Triggers

Bu konudan daha fazla soru