Question

Difficulty: EasyFlow Types and Triggers

Apex Health Services needs to automate business logic whenever a new Patient Intake record is created. An administrator must implement solutions for two distinct requirements:
1. Populate an initial Risk Assessment Score on the newly created record prior to saving it to the database.
2. Automatically create a follow-up Task record assigned to a care manager once the Patient Intake record has saved.

Which two Flow configuration choices should the administrator select to efficiently fulfill these requirements? (Select two answers.)

  1. A record-triggered flow configured for Fast Field Updates (Before-Save) to populate the Risk Assessment Score on the triggering record.Answer
  2. A record-triggered flow configured for Actions and Related Records (After-Save) to create the care manager Task record.Answer
  3. C
    A record-triggered flow configured for Actions and Related Records (After-Save) to set the Risk Assessment Score on the triggering record.
  4. D
    A Schedule-Triggered Flow running hourly to query recently created records and perform both tasks in a single batch loop.

Answer

The administrator should select Fast Field Updates (Before-Save) for populating fields on the triggering record prior to database commit, and Actions and Related Records (After-Save) for creating related Task records after the record is saved.
Selecting Fast Field Updates (Before-Save) ensures fields on the triggering record are modified in memory prior to database commit without extra DML queries. Selecting Actions and Related Records (After-Save) ensures the triggering record has been committed, enabling the flow to create associated child records such as Tasks.

Step-by-Step Solution

1
Analyze requirement 1: Setting field values on the triggering record prior to database commit.
Identify that updating fields on the same record before saving is best suited for a Fast Field Updates (Before-Save) record-triggered flow.
Before-save flows run prior to saving the record to the database, allowing direct field modification without issuing additional DML database operations.
2
Analyze requirement 2: Creating a separate, related record (Task) upon successful record creation.
Identify that creating related records requires an Actions and Related Records (After-Save) record-triggered flow.
After-save flows run after the record has been saved and assigned an ID, which is necessary when creating related child records or performing external system calls.

Key Concept

Selecting optimal Flow trigger optimization types (Before-Save Fast Field Updates vs After-Save Actions and Related Records) based on automation goals.
Rate this question