Section 4 · Business Logic and Process Automation
4.3 Build Flows and Select the Correct Flow Type
Exam objective
Create and configure flows using Flow Builder and determine an appropriate flow type for a business requirement.
Flow Builder is Salesforce’s declarative tool for orchestrating logic, user interaction, and record updates. A flow consists of elements connected by paths, with variables and resources carrying data. Start by deciding what initiates the work and whether a person must interact. A screen flow guides a user through questions or decisions. A record-triggered flow responds to record creation or update. A schedule-triggered flow processes records on a schedule. An autolaunched flow runs without screens and can be called by another automation, an action, or an integration where supported. Other flow types serve specific platform contexts; consult the current flow type list for release-specific options. For record-triggered automation, choose before-save behavior for efficient updates to the triggering record when only that record must change. Choose after-save behavior when the flow needs related records, actions, or further processing that occurs after the record is saved. Set entry conditions narrowly and decide whether the flow should run on create, update, or both. Use a decision element to branch on business conditions, and use Get, Create, Update, and Delete Records only when the design requires them. Avoid repeated queries or updates inside loops. Build in small, named steps. Use clear labels and descriptions, meaningful variable names, fault paths for recoverable errors, and subflows for reusable logic when they reduce duplication. Consider whether the flow runs in user or system context and what that means for access. User-facing flows should validate input and show useful messages. Record-triggered flows should be bulk-safe and should not assume only one record is processed in a transaction. Test with multiple records and realistic data.
Before activating, use Flow Builder’s debug options and test representative branches. Check interactions with other flows, validation rules, assignment rules, and legacy automation. Activation changes production behavior, so deploy the flow with dependencies and a rollback plan. Flow is powerful, but complex orchestration can become difficult to maintain; sometimes a standard feature or a small programmatic service is more appropriate.
Applied scenario: A sales manager wants a guided screen that captures a renewal request and creates a follow-up task. Use a screen flow because a user must provide information and see prompts. Collect and validate the renewal details, use a decision for renewal type, and create the task with an owner derived from the stated business rules. If the request can be started from a record, pass the record ID as an input rather than asking the user to find it again. Test cancellation, missing input, user permissions, and the resulting task assignment as a standard user. Design and risk review: A common design failure is choosing a screen flow for automation that should run without a user, or using an after-save flow when only same-record fields need updating. Loops with record updates can create limits and performance problems. Entry conditions that are too broad can retrigger downstream automation. Never assume debug as an administrator proves the flow works for the intended user. Check permissions, context, fault behavior, and the interaction with other active automation. Salesforce Certified Platform App Builder | SU ·26 guide alignment 16 Exam lens: First translate the stated requirement into a measurable outcome. Identify the actor, record or object in scope, timing, access boundary, and exception path. Eliminate choices that solve only the visible interface while missing the underlying data, security, or lifecycle requirement. Then compare the remaining supported features by fit, operational complexity, maintainability, and any dependency named in the scenario. A strong answer satisfies the stated need with the least fragile configuration and preserves the platform’s security and governance model. These are study heuristics, not additional official exam rules.
Extra concept: Treat configuration as a system rather than a list of settings. A field may participate in a formula, validation rule, flow, report, permission set, Lightning page, and deployment package at once. Before changing it, identify those dependencies, decide which are intentional, and test the full user journey. This dependency view explains why a locally correct change can still fail after deployment or for a different user. Use Setup dependency tools where available, source comparison, and focused regression checks; no single dependency view is guaranteed to reveal every runtime relationship.
Verification exercise: Turn the lesson scenario into a small test plan before calling the design complete. Record the starting data, the user permissions, the expected outcome, and the evidence that would confirm it. Test one ordinary path, one boundary condition, and one invalid or unauthorized path. Compare the result with the business requirement, then repeat after deployment in the target environment. This catches differences caused by data, activation, page assignment, sharing, or dependencies. Save the test cases with the release notes so another administrator can reproduce the result.
Key takeaways
- Create and configure flows using Flow Builder and determine an appropriate flow type for a business requirement
- Choose the platform feature that fits the requirement, data, access, and operating context.
- Test realistic users, exceptions, dependencies, and lifecycle effects before release.
- Official references: https://help.salesforce.com/s/articleView?id=005298964&language;=en_US&type;=1 https://trailhead.salesforce.com/content/learn/modules/flow-basics
