flow-patterns

Flow Patterns

SCOPE: AUTOMATION_ONLY - This skill applies ONLY to Flows (Record-Triggered, Screen, Scheduled, Platform Event-Triggered). DO NOT use this skill for Apex code or LWC components. For Apex patterns, use apex-patterns instead.

---

Patterns and best practices for building Salesforce Flows.

When to Use This Skill

• Building Record-Triggered Flows
• Building Screen Flows
• Building Scheduled Flows
• Building Platform Event-Triggered Flows
• Choosing between Flow and Apex

---

Flow Types Reference

Flow Type	Use When
Record-Triggered	Automate on record create/update/delete
Screen Flow	User-facing forms, wizards, guided processes
Scheduled	Time-based automation, batch-like processing
Platform Event-Triggered	React to events from external systems
Autolaunched	Called from Apex, other Flows, or Process Builder

---

Record-Triggered Flow Patterns

Pattern 1: Entry Conditions

Always use entry conditions to prevent unnecessary runs:

Entry Condition:
  - Status EQUALS 'New'
  - AND RecordType.DeveloperName EQUALS 'Standard'
  - AND IsProcessed__c EQUALS false

Pattern 2: Prevent Recursion

Use a checkbox field to prevent recursive execution:

Flow Start:
  Condition: IsFlowProcessed__c = false

Decision:
  Check if already processed

Update Record:
  Set IsFlowProcessed__c = true

Pattern 3: Before vs After Save

Timing	Use For
Before Save	Field updates on triggering record (no DML cost)
After Save	Creating/updating related records, callouts

Before Save - Fast, no DML counted:

Update triggering record fields directly
No "Update Records" element needed

After Save - Full capabilities:

Create child records
Update parent records
Send emails
Make callouts (with @future)

---

Screen Flow Patterns

Pattern 1: Multi-Step Wizard

Screen 1: Collect basic info
  → Assignment: Store in variables

Screen 2: Collect details
  → Assignment: Build record

Screen 3: Confirmation
  → Create/Update Records

Screen 4: Success message