An administrator has been asked to update a flow that was created as part of a recent update. When the administrator opens the flow for editing, the Flow toolbox offers only four elements…

Question

Options

• AThe flow is a screen flow.
• BThe version of the flow is inactive.
• CThe flow is a before save flow.
• DThe version of the flow is activated.

• A
  9% (3)
• B
  3% (1)
• C
  83% (29)
• D
  6% (2)

Explanation

Before-save flows (Record-Triggered Flows set to execute before a record is saved) are intentionally restricted to a small subset of elements - Assignment, Decision, Get Records, and Loop - because they run synchronously in a pre-commit context and cannot perform DML operations on other records or interact with the UI. This explains the limited toolbox the administrator sees.

Why the distractors are wrong:

• A (Screen Flow): Screen flows have more elements available, including Screen, Display Text, and other interactive components - not fewer.
• B (Inactive version): A flow's activation status has no effect on which elements appear in the toolbox; inactive and active versions have the same element options.
• D (Activated version): An activated flow is locked from editing entirely (you'd need to save a new version), but activation status doesn't restrict which elements are available.

Memory tip: Think "Before Save = Basic Only" - before-save flows get only the four bare-bones logic elements (Assignment, Decision, Get Records, Loop) because they're too early in the transaction to do anything beyond reading and evaluating data.

No community discussion yet for this question.