Salesforce Summer’22 Release is here. You can take a quick look in the release updates here. While the post cover points related to Admin and Developer both, I think Flow needs a separate post. As you can say its major focus area in recent releases. So today we will check some of the highlighted related to Salesforce Summer’22 Flow Updates.
We can now use Formulas in a record-triggered flow. Previously we can only refer fields. Using Formula we can easily make conditions. Click Check Syntax after you build each expression because the formula builder shows one error at a time.
We can now create collapsible section and provide header in Flow screens. Just drop the section check the include header and provide details.
We can now use Name and Address field on Flow screens. Autocomplete is available in Address record fields. When we add a record field to a flow screen, the name, data type, help text, required, and, in some cases, existing values are automatically configured. Record fields (beta) uses record variables to determine which fields can be placed on a flow screen and their configuration.
We can now manage Run Order of record triggered flow using Flow Trigger Explorer. We don’t need to open edit flow and update the order instead we can drag and drop flow in new order.
We can now create Flow from the Flow Trigger Explorer. It will pre-filled settings based on the category and context.
We can now Access record triggered flow and Flow Trigger Explorer from the Object Manager.
We can now do Automated Testing of record triggered flow. From the Debug run we can create a Flow Run. We can set multiple assertion to verify that the flow and check how flow was executed and how the variables are updated.
We can also set the Initial record or can manually set the field values.
Flow tests have these beta limitations and considerations.
- The maximum number of tests per flow is 200.
- Flow tests are available only for record-triggered flows.
- Flow tests support only flow paths that run immediately.
- Packaging and change sets aren’t supported for flow tests.
- Flow tests don’t support testing other automations such as Apex or other record-triggered flows.
- The owner of the triggering record in a flow test changes to the last person who edits the test.
With the Winter 23 release, two column layouts are ignored. Instead we should use the section component with multi column layout. We can make up to four columns directly in the screen.
The Migrate to Flow tool now supports more type of workflow. In Spring ’22, the Migrate to Flow tool supported workflow rules that contained these items:
- Field-based criteria
- Field updates
- Email alerts
- Outbound messages
- Time-dependent workflow actions
- Rule criteria formula that’s set to true (unless evaluation criteria is also set to created, and any time it’s edited to subsequently meet criteria)
In Summer ’22, the Migrate to Flow tool now also supports:
Not equalto null
- Rule criteria formula
Formulas that use
$RecordType aren’t supported. You can check how you can setup this here.
We can now send a message to a Slack channel, a direct message, or the Messages tab of a Slack app that includes a button that a recipient can use to launch a flow.
These are some of the updates which I like most about the Salesforce Summer’22 Flow Updates. So which flow update you liked most, let me know in comments. Happy Programming 🙂