Flow versus Flow Orchestration for multi-team financial processes
Key Takeaway
Flow Orchestration coordinates flows instead of replacing them. Keep the flows that do each piece of work, and let one orchestration move the work between users and teams. Put parallel work in concurrent steps inside one stage.
Flow and Flow Orchestration both automate business processes, but they solve different problems. A flow automates a record-centric process, such as updating records or collecting data on a screen. An orchestration combines and coordinates a series of flows into one multi-step process that hands work between different users, teams and systems, such as a mortgage approval. A design for a process that moves between teams uses both: flows do each piece of the work, and an orchestration coordinates them.
What a flow does
A flow is an application that automates a business process by collecting data and doing something in your Salesforce org or an external system. You build flows in Flow Builder, a point-and-click tool.
Flows can show screens to guide users. A flow that shows screens is a screen flow. Flows can also look up, create, update and delete records for multiple objects. Flows aren't tied to any one object, but they are record-centric.