This week I will give you an overview of the Flow Orchestrator. This tool is possibly the most important tool that is going GA (generally available) with the Spring 22 Release.
I watched the Salesforce Spring 22 Release Readiness webcast for Admins on Friday. It was a great webcast.
Flow orchestrator is one of the topics that caught a lot of attention. Rightfully so! According to the Salesforce team, the use cases for the Orchestrator are:
- Handoff of tasks between users and teams.
- Multiple flows running parallel.
If your use cases don’t require any of these items, flow should be sufficient for you.
This simplified definition of the Flow Orchestrator is missing two important superpowers that we did not have before this release:
- Orchestrator supports on-screen user interactions that are triggered by object create/update.
- On-screen interactions can be delayed/scheduled based on triggers.
There are two types of Orchestrations:
Orchestrations include stages consisting of one or multiple steps, each step pointing to one autolaunched or screen flow. They can also have decisions to determine what needs to be executed depending on various scenarios.
With the introduction of the flow Orchestrator, I can say flow is a skill that can keep you busy full time. I don’t know if this is the case already, but you could freelance just building Salesforce flows.
Getting started on the Orchestrator is quite intimidating.
You may be wondering what you need to do to prepare yourself for them. I will tell you: If you don’t have the fundamental knowledge of process, and have not done any process mapping, get started with that now. This is not for the faint-hearted.
When you click on create Ligtning App or Record-Triggered flow button in Salesforce you are greeted with a configurator.
You get a blank canvas when you choose to create new Orchestration.
Help menu takes you to the standard flow help pages linked to Orchestrator help pages that offer minimal information.
There are advanced features that come with the Orchestrator. If you want, you can set entry and exit conditions that determine when each step in your flow is considered completed. This allows for enhanced functionality, but increases complexity at the same time.
I will give you more information as I experiment with Flow Orchestrator further.
P.S. Originally published on 02/06/2022.
Read the previous issue of the newsletter here.
Read the next issue of the newsletter here.
Subscribe to the weekly educational Salesforce Flow Tips newsletter here.