Section 8 · Process Automation · 20% of exam
8.1 Choosing Flow, approvals, formulas, and legacy automation
Exam objective
Given a complex scenario, determine the best declarative tool or combination of tools; explain capabilities and limitations of each declarative automation tool.
Translate the process into trigger, decision, action, interaction, and approval needs. A formula field calculates a value from other data when displayed or queried and is appropriate when the result should remain derived rather than stored independently. A validation rule prevents a save when a condition is not met. Flow supports record-triggered, scheduled, screen, and other automation patterns, allowing decisions, assignments, updates, actions, and user interaction. Approval processes route records for formal review and capture approval state; they are not general-purpose workflow builders. Record-triggered flows are suitable for automating work when records are created, updated, or deleted within supported contexts. Before-save flows are efficient for updating fields on the triggering record because changes can be applied before the record is saved. After-save flows are used when the automation needs related records, actions, or post-commit work. Scheduled paths can delay actions relative to a record date or time. Choose entry conditions carefully, and use prior-value checks when an action should occur only on a transition rather than every update.
Screen flows guide a user through an interactive process and can validate or collect information. They are useful for guided tasks, but the flow's screens and components must be accessible and security-aware. Flow can run in user or system context depending on type and configuration; this affects data access and must be designed deliberately. A flow that can read or update data beyond the invoking user's access needs careful justification, field-level security review, and safeguards against exposing values on screens or in error messages.
Approval processes are designed for record submission, approval steps, assigned approvers, recall or rejection behavior, and final actions. They are appropriate when a record needs a formal decision trail. A flow can support routing and orchestration around an approval, but duplicating approval status and logic across unrelated automation can create inconsistent outcomes. Define who can submit, approve, delegate, recall, and edit a pending record. Test the entire approval lifecycle, including rejection, reassignment, and changes made while pending.
Workflow Rules and Process Builder are legacy automation tools for existing orgs. Salesforce has directed customers toward Flow for new automation, but existing workflow rules and processes may still run and interact with flows. Do not migrate blindly; inventory what exists, understand timing and behavior, compare with Flow capabilities, and test before deactivating legacy automation. A consolidated Flow can reduce fragmented logic, but a large flow with many unrelated branches may be hard to maintain. Use clear names, descriptions, subflows where appropriate, and a documented owner.
Select tools by functional fit. Use formulas for derived values, validation for save-time constraints, Flow for event-driven and guided automation, and approval processes for formal decisions. Consider whether the task is declarative, whether it requires complex transactions or unsupported behavior, and how errors will be observed. An external system or Apex may be appropriate when declarative tools cannot meet a defined requirement, but do not jump to code without checking supported Flow capabilities and limits.
Exam focus: compare tools by trigger, interaction, persistence, approval, and transaction behavior. Notice whether the requirement is a calculated value, a blocked save, an automated update, a user-guided process, or a formal approval. For complex scenarios, combine tools only where each has a clear responsibility. Avoid unnecessary automation if a standard field, formula, or native feature already meets the requirement.
Salesforce continues to evolve Flow capabilities. Verify current feature availability, limits, and migration guidance for the org's release before planning a conversion.
Maintain an automation inventory that records purpose, trigger, owner, affected objects, dependencies, and error route. Before adding a new automation, search for existing flows, approval processes, workflow rules, and processes that update the same fields. Consolidation is useful when it clarifies ownership, but a single sprawling flow can be difficult to test. Use naming conventions and descriptions; define entry conditions in business language; and review flow order when several record-triggered flows share an object. Measure outcomes, not just whether the flow interview completed. Practical scenario
When an opportunity's discount exceeds a threshold, a sales manager must approve it, and the expected margin should display from price and cost. Use a formula for derived margin, an approval process for the formal approval decision, and Flow only for supporting actions that are not already handled by approval behavior. Prevent users from editing protected values while pending using appropriate permissions or validation. Test submit, approve, reject, recall, and resubmission paths.
Extra concept
Automation observability is an additional design requirement. Decide how failures are surfaced, who receives fault notifications, how a failed record is retried, and where operational evidence is stored. A process that silently fails is not complete even if its happy path works.
Key takeaways
- Use formulas for derived values, validation for save constraints, Flow for automation, and approvals for formal decisions.
- Choose before-save or after-save flow behavior based on the action required.
- Inventory existing automation before adding or migrating logic.
- Official references: https://help.salesforce.com/s/articleView?id=005298969&language=en_US&type=1 https://help.salesforce.com/s/articleView?id=sf.flow.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.approvals.htm&type=5 https://trailhead.salesforce.com/content/learn/superbadges/superbadge_flow_optimization
