Flow Orchestrator

⚡ 1-Minute Summary Follow the hierarchy: Start with simple configuration, then move to Flow, and only use Apex when strictly necessary. Choose the right trigger context: Use before-save to update fields on the record being saved. Use after-save when updating related records, sending notifications, or running async paths. Protect your governor limits: Never place queries or DML statements inside loops. Collect records into collections and execute a single DML operation outside the loop. Module Map: The Complete 360° Automation Architecture MODULE ROOT: 'Which automation tool should you use, and will it survive bulk processing?' ├── Flow Types: 5 core flavors for 5 distinct execution contexts ├── Flow vs. Apex Decision Matrix: Complexity and governor limits threshold ├── Bulkification & Recursion Guards: Preventing the #1 Flow failure mode ├── Before-Save vs. After-Save Cost: Zero extra DML vs. an additional save cycle...

In plain words: Salesforce Flow Orchestrator is a workflow automation tool designed for long-running, multi-person business processes. While a standard Flow runs for a single user in one session, an Orchestration strings together multiple Screen Flows and background Autolaunched Flows into sequential or parallel Stages and Steps —assigning tasks to different teams (like HR, Finance, and IT) over days or weeks and displaying them in the Work Guide component. Standard Salesforce Flows excel at automating real-time field updates, screen forms, and trigger operations for individual users in a single transaction. However, complex enterprise processes—such as employee onboarding, contract approvals, or multi-departmental claims processing—often span multiple days, involve hand-offs across distinct teams, and require sequential and parallel approvals. Salesforce Flow Orchestrator provides a dedicated workflow orchestration layer that coordinates multi-user, multi-step bu...