Salesforce released the Spring’22 release notes a couple of weeks ago. As we have observed in the last few releases, this release will also bring a ton of new exciting updates to Salesforce Flows. Here are some of my favorite salesforce flow features in this release Watch the below two quick videos or read the summary in this article.
Collection Filter
With this brand new out-of-the-box flow component, you will now be able to specify criteria when using the get records component or be able to further filter your collection using this collection filter. Using a collection filter will also allow you to avoid running into the ‘Iteration Limit Exceeded’ flow error as it opens up the governor limit to handle a larger set of records. For more information or demo look at the first video or click here.

Flow Trigger Explorer
If I have to select only one favorite feature of this entire release, it would be Flow Trigger Explorer. This provides Admins and Developers a quick glance at what all triggered flows exist for a particular object so that they can decide which one to pick for the new user requirements. Like Apex trigger, Record trigger flows also consume a great amount of CPU time and can get difficult to maintain at times if your org has many record triggered flows. But with this new tool provided by salesforce, it would be lot easier to make decisions and avoid creating multiple triggers on the same object. Take a look at this demo for a quick overview of this new tool by salesforce.

Workflow to Flow Migration tool
As promised by salesforce during the Winter’22 release, Salesforce now has provided a Pilot tool that allows organizations to migrate workflow rules to Salesforce Flow. This is very helpful for the orgs with many workflow rules, as salesforce announced that they deprecate Workflow rules as well as Process builders in near future.

Control order of execution for the triggered flows
With the Spring’22 release, Salesforce will allow you to define the order of execution for the triggered flow. You will be able to put numeric value flows on the same object and trigger. Some of the key points to keep in mind.
- Flows with the same trigger (before- or after-save) on the same object with trigger order values from 1 to 1,000 run in ascending
order (1, 2, 3, and so on). Multiple flows with the same trigger order value run in alphabetical order based on the flows’ API nam - Flows without trigger order values run next and in the order of their created dates. Flows in Winter ’22 and before run and continue
to run in this order, unless you define a trigger order value for them. - Flows with trigger order values from 1,001 to 2,000 run next and in ascending order. Any ties are settled using the flows’ API names
Salesforce announced that their team is working on marrying this feature with salesforce flow explorer tool as shown above for drag and drop reordering ability.

Trackbacks/Pingbacks