The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Using Flow Orchestration to coordinate multi-step business processes (opens in a new tab)

You will understand how Flow Orchestration organizes stages and steps across automated and interactive work, and when it is better than chaining several Flows.

Why read this

The article gives a worked onboarding example and a short checklist for a first build.

  1. Automated Flow stage
  2. Interactive Screen Flow stage
  3. Automated provisioning stage
A Flow Orchestration advances to the next step only when the previous one completes

Most automations start as one Flow, but as a process grows, several Flows can conflict, run out of order or duplicate work. Flow Orchestration, which the article describes as generally available in recent releases, lets you build one process made of stages and steps, where each step is an automated Flow, a background Apex or invocable action, or an interactive Screen Flow or approval assigned to a user or queue with a due date.

An orchestration advances to the next step only when the previous one completes. If a step fails, the orchestration pauses rather than continuing silently, and the orchestration run record shows the current stage, step, assignee and status in one place. The author’s onboarding example has an automated stage that creates tasks and a project, an interactive stage where a specialist confirms a kickoff call within three days, and an automated stage that provisions a portal user and sends a welcome email.

The article says orchestration suits processes with handoffs between people and automation, such as approvals, onboarding, case escalation and quote-to-cash, and is excessive for a single condition-and-action rule. It advises mapping the process on paper first, keeping one job per Flow, and remembering that orchestration runs consume Flow interviews and so still need governor-limit planning.

Read the original at dev.to (opens in a new tab)

Worth reading?