Section 8 · Automation · 15% of exam
8.2 Flow capabilities, types, configuration, and order of execution
Exam objective
Describe Flow use cases and configuration, including screen flows, record-triggered flows, autolaunched flows, and order of execution.
Screen flows guide a user through screens and inputs. Record-triggered flows run when records are created, updated, or deleted according to configuration. Autolaunched flows run without screens and can be invoked by other automation or processes. Select based on whether user interaction is needed and what event starts the work. Use entry criteria to limit a record-triggered flow to relevant changes. Consider whether it should run before or after the record is saved, what records it reads or updates, and whether it can cause recursion or interact with other automation. Add fault handling where appropriate and avoid unnecessary queries or repeated updates.
Use Flow Builder tools to inspect the flow, debug representative inputs, test both expected and fault outcomes, and verify as the intended user. Order of execution matters because validation rules, flows, assignment, and other automation can affect the same transaction.
Additional concepts
Screen, record-triggered, and autolaunched flows
A screen flow guides an interactive user through inputs. A record-triggered flow starts from a configured record event and criteria. An autolaunched flow runs without a user-facing screen and can be invoked by another process. Choose based on how the work starts and whether a person must interact.
Execution and troubleshooting
Before-save and after-save record-triggered flows serve different update needs. Entry criteria help limit unnecessary runs; updates to triggering records can interact with other automation or cause repeated execution if not designed carefully. Debug with realistic inputs, inspect fault paths, and verify the result after related automation has run. A user must enter missing details before submitting a request, while a status change should trigger background routing. Use a screen flow for guided input and a record-triggered flow for the automatic response to the saved record.
In exam scenarios, identify both the trigger and whether the process requires a screen before choosing a flow type.
Key takeaways
- Screen flows are interactive; record-triggered flows start from record events; autolaunched flows run without screens.
- Entry criteria and order of execution affect behavior and performance.
- Debug success and fault paths with representative records and users.
