Newsletter

May/June 2022 Content Announcement

Hello folks,

I dedicate this newsletter issue to the announcements for new content coming from me next month (May & June):

On 5/31/2022, I will broadcast a live session with my fellow content creator Melody Lwo, a.k.a. Flowsome, on YouTube and LinkedIn. The session has been posted, here on my Salesforce Break YouTube channel and on my LinkedIn profile.
I will answer flow questions during our monthly Flow Office hours session with Terry Miller on 6/10/2022. Register for the Flow Office Hours Here.
I am the leader of a brand new Trailblazer User Group for Architects. I will host Antoine Cabot, Senior Director of Product Management in Salesforce, on 6/15/2022. Antoine is leading the Orchestrator and Flow for Slack initiative. Register for the Architect session here.
I will present in Atlanta at Southeast Dreamin’ a session titled “Flow Trigger Explorer and Orchestrator”. You can find the Dreamin’ session details here and register for the event.

Now let’s get back to reading the Release Notes. Summer 22 will be in all of our Orgs soon.

Enjoy.

P.S. Originally published on 05/17/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.

Newsletter

The Orchestrator Vision

Hello folks,

I presented at Texas Dreamin’ two weeks ago. I shared a use case I implemented using the Orchestrator.

The main message of my presentation was to think big when you are working with the Orchestrator.

There are a few reasons for that:

The Orchestrator is not free. You should solve a decent-size problem to get a return on your implementation.
The tool is complicated. If your use case is not complex, the chances are you will find a way of implementing it with flow and admin tools.
The Orchestrator is powerful when you are coordinating tasks going between the silos of the organization.

There were a few observations I shared:

The Orchestrator is not an excellent approval process replacement. It does not lock records, and it is harder to implement. Furthermore, Salesforce said the approval process wouldn’t go away.
This solution works best when you need to schedule or delay user screen interactions which were not possible before.
The tool also can send tasks to users, groups, or queues, which means you will need a broad implementation scope to make the best out of it.

What was the use case I presented?

First, the salesperson wins an opportunity; then, the system checks whether the product in the opportunity line item is in the inventory or not. Next, the automation asks management to approve the order fulfillment and the production request if there is insufficient inventory. Finally, the Orchestrator will create a contract and an order for the opportunity, then a work order to get the item produced if necessary and shipped right after.

Overarching broad processes like these are great for the Orchestrator.

I think it is important to think big before tackling the Orchestrator canvas.

Let’s remember you will be much better off mapping your process before you implement it using this tool. Things will get complicated.

Check out my process map for the use case on top of this page.

Enjoy.

P.S. Originally published on 05/10/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.

Newsletter

Flow Orchestrator in Spring 22

Hello folks,

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/public-group/queue targeted interactions that are triggered by object create/update.
On-screen interactions can be delayed/scheduled based on triggers.

There are two types of Orchestrations:

Autolaunched
Record-Triggered

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.

Salesforce Break

Salesforce Made Easy

Tag Archives: Orchestrator