Insights

Winter ’22 Salesforce Release Gem: Top 5 Flow Changes

“There’s a whole lotta flowin’ goin’ on in Salesforce’s Winter ‘22 release!”

– Erin Freed

This release will make a whopping 23 changes to Flow Builder and Flow Debugging, plus several more to Flow Management and Extensions.

As a flow builder myself, I was thrilled to find many of my pet peeves will be addressed in this release. Thank you, Salesforce! Here are my Top 5 flow changes in the Salesforce Winter ’22 release:

1. Debugger: Change Record Field Values From the Debug Screen

Why the Change?

If you’ve ever tried to debug a flow triggered by a record change, you know what a pain it is, especially if the flow is triggered by an ‘Is Changed’ operator. The debugger doesn’t track all the steps, and you’re on your own to troubleshoot. Not fun.

What’s New?

You can finally make the field update you need directly from the Debug window. The debugger will now show you the flow’s response to your ‘Is Changed’ operator.

How Do You Use It?

Now, when you Debug, you’ll see the screen below.

(1) Just select “Run the Flow As If the Record is: Updated”

(2) Select your record.

(3) Make the field update you want to test as the trigger, and click “Run.”

Piece of cake! The debug will run as if your update was made.

debug flow builder

Where is this change applied?

This change applies to Lightning Experience and Salesforce Classic in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.

2. Flow Builder: Send Outbound Messages from Record-Triggered Flows

Why the Change?

Finally! You can now send Outbound Messages as core actions from flows. That means you can retire all those cranky old workflows that are hanging around. Time to clean house!

What’s New?

Outbound messages are now available as core actions in flows that run after the record is saved. So, now you can send a SOAP message from a record-triggered flow to an external recipient through a flow.

How Do You Use It?

See the screenshot below.

(1) Drag an Action element onto the canvas.

(2) In the Action field, begin to enter “outbound.” Select the outbound message action with the object type of the triggering record, for example, Case.

(3) You don’t need to enter input parameters because the triggering record’s ID is passed to the outbound message action automatically. Yay!

(4) Then, after the flow runs, go to the Outbound Messages page in Setup to confirm that the message was sent.

Where Is This Change Applied?

This change applies to Lightning Experience and Salesforce Classic in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.

3. Flow Builder: Call a Subflow from a Record-Triggered Flow

Why the Change?

How many times have you wished you could just call a Subflow from a record triggered flow? Simple, right? Unfortunately, it hasn’t been…until now.

What’s New?

With the new Subflow element, you can now build record-triggered flows with Subflows to run after a record is saved or before a record is deleted. So, you can break those big complex flows into smaller Subflows and call them as needed.

For example, when an opportunity is created, you perform a series of updates in a record-trigger flow but you also need to perform complex logic, subject to change, to assign the opportunity owner. You can now create a separate flow to handle the assignment logic and call it in your starting flow.

How Do You Use It?

First, create an autolaunched flow to perform a common task. Add your input and output variables based on sObjects of the same type.

Then create or open an existing record-triggered flow. Drag the new “Subflow” element onto your canvas. Select the Subflow, and assign the values of the $Record and $Record__Prior global variables to the input and output variables. When the record-triggered flow executes the Subflow element, the triggering record’s values will be available in the flow’s $Record and $Record__Prior global variables.

Where Is This Change Applied?

This change applies to Lightning Experience and Salesforce Classic in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.

4. Flow Builder: New “Roll Back Records” Element

Why the Change?

In some situations, if a flow element fails, you WANT the system to save the pending changes, but in other situations, you DON’T. Before Winter ‘22, you didn’t have a choice. When a transaction ended, its pending record changes were saved even if one of the flow elements failed. Ouch!

What’s New?

There’s a new “Roll Back Records” element that you can add to your path.

EXAMPLE:

In the diagram below, if the flow fails to create the appointment, it executes the Roll Back Records, so the pending lead won’t be saved to the database. 

Without the Roll Back Records element, if the flow failed to create the appointment, it would create the lead without an appointment. The choice is now yours!

roll back

How Do You Use It?

Simply add the Roll Back Records element to your flow in the spot you want it, and poof! Your dreams will come true!

Where Is This Change Applied? This change applies to Lightning Experience and Salesforce Classic in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.

5. Flow Builder: Supercharge Your Scheduled Paths with Minutes and Batches

Why the Change?

If you’ve ever tried to schedule a path to run in minutes, you know you had to come up with that pesky formula to convert hours to minutes. Now you don’t have to.

And, as a bonus, you also don’t have to worry about hitting the Apex governor limits. Woo Woo!

What’s New?

When you need a scheduled path based on a time source, like when a record is created or updated, or the value of a date/time field, you can now schedule that path in minutes.

And you can set the batch size to avoid hitting a per transaction Apex limit. For example, if you set your batch size to two and seven records are scheduled to be processed in the same minute, Flow Builder will group them into four batches.

How Do You Use It?

See the screenshot below. Configure a scheduled path for a record-triggered flow that runs after the record is saved.

(1) Specify the number of minutes before or after the time source for your scheduled path to run.

(2) Set a batch size smaller than 200 to improve your performance.

Where Is This Change Applied? This change applies to Lightning Experience and Salesforce Classic in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.

One more cool Flow Change – Another valuable Flow change in the Winter ‘22 release is that Salesforce will now help you decide if your flow should launch before or after a record insert/update. How cool is that? Check out our blog on it, “Optimizing flow execution with start element change.” 

For further details on all the Winter ‘22 changes, here’s a link to the Salesforce Winter ’22 Release Notes.

Author: Erin Freed, Salesforce Consultant

The EightCloud team has been a truly amazing vendor to work with. The team members are very professional, provide everything on time or ahead of time and they have extensive technical knowledge. Working with the team was a breeze. They easily understood our requirements and provided us an even better solution than we expected. This has tremendously helped us be more efficient and allowed us to focus on actual work. Definitely recommend hiring this team!"

- Netsey Tefera, Zero to Three

Let us craft a custom solution that will meet your current and future Salesforce needs and make your life easier.

Insights

Rotate Your Device

Partners and friends, we are proud to share the new EightCloud brand and website with you. Our transformation reflects our commitment to helping you achieve Salesforce excellence through a focus on efficiency, expertise and genuine partnership.

We wish you the best and look forward to connecting with you soon!

Show me the new site!