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…

A before-save record-triggered flow is designed to make fast field updates to a record before it is saved to the database. To ensure high performance, Salesforce intentionally limits the elements available in the toolbox for this type of flow. The only available elements are for logic and data manipulation directly related to the triggering record: Assignment (to change field values), Decision (for branching logic), Get Records (to query related data), and Loop (to iterate over collections). Elements that perform actions, interact with the user interface, or modify other records are excluded.

A. A screen flow would have many more elements, most notably the 'Screen' element, which is used to build user interfaces.

B. The active or inactive status of a flow version does not alter the set of available elements in the Flow Builder toolbox.

D. Similar to the inactive status, a flow being activated does not change the elements available for editing within the Flow Builder.

---

1. Salesforce Help, "Record-Triggered Flow Considerations": Under the section for before-save flows, the documentation explicitly states, "In a before-save flow, you can add these elements: Assignment, Decision, Get Records, and Loop." This directly confirms the scenario described in the question.

2. Salesforce Help, "Flow Element: Screen": This document describes the Screen element, which is a core component of Screen Flows but is unavailable in record-triggered flows, especially before-save flows, as they run without user interaction.

3. Salesforce Help, "Flow Core Action: Send Email": This document details an 'Action' element. Actions are not available in before-save flows because they can introduce delays and perform operations outside the scope of updating the triggering record. This illustrates the type of element that is intentionally excluded.