10 New Salesforce Flow Features in Summer ’22

Share this article...

With the Summer ‘22 release fast approaching, Salesforce have now dropped the release notes, including the full low-down of what’s new in Flow.

With Process Builder and Workflow Rules going through a phased retirement, we should all know by now that Salesforce Flow is the future of Salesforce automation. This release contains lots of goodies (I’ve highlighted my top 10), so without further ado, let’s go with the flow…

1. Formula Entry Conditions for Record-Triggered Flow

Similar to Process Builder, Salesforce is introducing the ability to trigger a flow based on a formula. If a formula evaluates to true, the flow will run – otherwise it won’t be triggered.

With this release, you can now migrate Workflow Rules that were triggered by a formula to Flow, using the migration tool. You may find the following resources helpful:

2. Custom Icons for Apex-Defined Invocable Actions

If you call Apex code in a flow, you can now add your own icon to these. This will be helpful on the canvas to see which code is calling which system.

READ MORE: Add Custom Icons to Apex-Defined Invocable Actions

3. New Features for Screen Flows

Section Headers

There are lots of goodies ahead for Screen Flows. First up, we have section headers to give collapsible sections – you guessed it – a header (similar to page layouts).

Screen Flow Supported Fields

In this release, the fields supported by Screen Flows using fields (Beta) have expanded to support Name fields and Address fields.

Accessibility Improvements

There have also been improvements with screen readers within the Flow Builder to enhance the experience of those with accessibility needs.

Historically, you could set a flow to run with two columns – this will be ignored from Winter ‘23, with the suggestion to move to the section component instead.

This component acts as a replacement for columns, with up to four columns supported.

Dependant Picklist Component

The dependent picklist component has been rebuilt as a Lightning Web Component (LWC), with minimal styling changes. This makes it easier for the system to support, and uses the latest technology with Salesforce migrating more to LWC – the next generation of Lightning Components.

Check out the resources below:

4. Other Flow Builder Enhancements

When building a flow, you can choose either free form or auto layout.

When using auto layout, components that are connected without a line are now highlighted when selected – this makes it easier to find them on the canvas.

If you are using custom labels, from Summer ‘22 you should notice the performance of the Flow Builder is improved. Visit the following pages for further details:

5. More Options in Flow Trigger Explorer

In the recently-launched Flow Trigger Explorer, you can edit the order of flows using a drag-and-drop tool.

From here you now have the option to create a new flow. New keyboard shortcuts have also been added to make moving around the interface even easier.

From the Object Manager, you can now see Flow Triggers with a shortcut to the Flow Trigger Explorer.

Salesforce offers useful documentation on the following topics:

6. Flow Testing

Using the new View Tests (beta) option in Record-Triggered Flows, you can create your own tests to check your automations before you make them live.

READ MORE: Test One, Two, Three, Flow (Beta)

7. API Version 55.0

As with all releases, Salesforce have incremented the API version by 1 to 55.

This changes the behaviour of merge fields in some instances, so be sure to check out the release notes for further details about the change.

READ MORE: Flow and Process Run-Time Changes in API Version 55.0

8. Run Screen Flows in Slack (Beta)

You can now send a message in a Slack channel, direct message, or the messages tab to launch a flow.

This will appear to the recipient as a button – when pressed, this will launch the specified flow.

We’d love to hear your use cases for this in the comments below, such as filling in a form when a record is updated by an integration!

READ MORE: Send Screen Flows to Slack with an Invocable Action (Beta)

9. Delete Flow and Process Versions from Managed Packages

AppExchange partners can now delete a Flow or Process Builder version from a managed package (in your packaging org) to help keep things tidy, and avoid releasing a deprecated version of an automation by mistake!

READ MORE: Delete Flow and Process Versions from Managed Packages

10. Flow and Process Release Updates

With this release, Salesforce have announced some new release updates, as well as some updates to others in terms of their enforcement dates.

Be sure to check out the details carefully and run a test in your sandboxes before enabling in production – prior to the auto activation date!

There video from Salesforce will help with this topic, as well as the following resources:

Summary

With the Summer ‘22 release, Salesforce is treating us to a host of new features and functionalities for Flow.

Enhancements will be hitting production orgs from May 20, with sandboxes being upgraded from May 6.

Don’t forget to share your favourite Flow features below!

READ MORE: The Complete Guide to Salesforce Flow in 2022

9 thoughts on “10 New Salesforce Flow Features in Summer ’22

  1. I’ve been working on the slack flow process. Right now it doesn’t look like you can pass recordID’s through, and the only fields supported are picklists and radio buttons (no text inputs). It’s not really worth it right now, feels like it’s been released too early.

    1. Hello David,

      Yes this is currently limited to Picklist Components and Radio Buttons and can’t consume a record ID either (at least natively).

      Fingers crossed this improves as it’s a new feature and is currently in Beta!

  2. For the section headers, it would be nice to have an option in the screen component to either collapse or expand the section after the client clicks the button on the object. If I have multiple sections on one screen element, it would look better to have the first section expanded then the remaining sections collapsed instead of expanding all sections. It looks cleaner this way.

    1. Hello,

      I agree with this suggestion and if it’s something you’d like Salesforce to consider implementing then please feel free to raise this as an idea on the idea exchange.

      If you are to share the URL for this idea, I’d happily give it an upvote.

Add Comment