Flow Orchestration versus a single flow for multi-user processes
Key Takeaway
Pick an orchestration, not a single flow, when a process needs several people or departments to do interrelated work, in order or in parallel.
A single flow automates one part of a business process, such as updating records or guiding one user through screens. Flow Orchestration combines and coordinates a series of flows into one process, called an orchestration. An orchestration hands work between different users, teams and systems.
Flow versus orchestration
A flow is record-centric. It collects data and acts in your org or an external system. It can look up, create, update and delete records on multiple objects. It can also show screens to guide a user.
An orchestration is user-centric. It coordinates a series of flows so that one process can span different users and different parts of the organization. Orchestrations run on the same Flow engine as flows, but they solve a different problem.
For example, imagine an online credit card application. A screen flow can power the application form. After submission comes the review, which covers risk analysis and Know Your Customer compliance checks. The review is a separate process that involves other people. An orchestration can combine these automated processes into a single workflow.