Flow Orchestration is used to combine multiple automated process into a single workflow. This is used when a business process requires collaboration between multiple teams. It joins multiple flows and maps how each flow interacts with one another. Each flow will be turned into a step and organized into stages. This article presents an overview of Flow Orchestration in Salesforce.
To access Flow Orchestration, follow the below steps,
- Navigate to Setup, enter Flows in the Quick Find box, then select Flows.
- Click New Flow, All+Templates, then Flow Orchestration.
- From New Flow, select one of two orchestration types: Autolaunched Orchestration (No Trigger) or Record-Triggered Orchestration.
Flow Orchestration list views
- Flow Orchestration includes two list views for tracking ongoing orchestrations: “Orchestration Runs” and “Orchestration Work Items.”
- We can access these two items from the Applauncher.
- Administrative supervisors can monitor the active orchestrations through the Orchestration Runs list view. Additionally, by clicking the arrow adjacent to any in-progress orchestration run, you can choose to either cancel or initiate debugging for the runs.
- End users mainly interact with Flow Orchestration through work items. When a user is assigned a work item, they receive an email notification. From this notification, they can click to the record page which contains the corresponding work. They can also access all of their assigned work items from the Orchestration Work Items list page.
Building blocks of Flow Orchestration
- Stage
An orchestration must contain at least one stage. Within a stage, there exists a grouping of associated actions or steps that you intend to organize. These steps may involve interactive tasks requiring user engagement or background processes functioning without direct user interaction. Conditions determining the completion of each stage are configurable, allowing you to specify criteria that must be met.
- Step
Steps are organized within stages and can be executed either sequentially or concurrently. Interactive steps demand user engagement, while background steps operate without requiring direct interaction.
Background steps invoke an autolaunched flow executed by the system. They can operate either synchronously or asynchronously, devoid of any user interaction.
- Interactive steps involve a designated user and the execution of a specified screen flow.
- An administrator includes the Flow Orchestration Work Guide Lightning App Builder component on the page layout corresponding to the record type where an individual can fulfill the interactive step assigned to them.
- When an orchestration initiates an interactive step, the assigned user receives an email containing a link to their designated action.
- The assigned user then clicks the link to access the record, where they can complete their task within the Work Guide.
- Flows
All steps require a flow in order to run. An interactive step is associated with a screen flow, while a background step utilizes an autolaunched flow. An evaluation flow can be employed to initiate a step or to mark an interactive step as concluded.
- Work item
When an interactive step runs within an orchestration, it generates a “work item” and assigns it to a user, group, or queue. Subsequently, the orchestration dispatches an email containing a link to the designated record page to all assigned users. Users then complete the assigned work item through the Orchestration Work Guide.
We have covered an overview of Flow Orchestration in Salesforce. To learn more Flow Orchestration (salesforce.com)
Take Five Consulting is a technology company, based in Virginia U.S., that specializes in the Mortgage Banking vertical especially LOS implementation and application development. Take Five Consulting creates and implement mortgage technology and software specifically for Mortgage Industry.
