🧿 Use of In and Not In Operators in Flows
With the new In and Not In operators, a flow accesses a collection of values to get related records without using the control element (Loop Element). The flow uses less SOQL queries and DML statements and executes more faster. The new operators used to access the Text, Number, Date, Date/Time, Currency, and Boolean collections of type . These In and Not In operators are available in the Get Records, Update Records, and Delete Records elements of the flow builder.
Why we use: The In operator to ensure your flows don’t exceed governor limits . For example, given in the screenshot below, a flow gets all related contacts if their role equals Decision Maker and if their related accounts have a shipping state in California. With the new In operator, the flow performs the Get Records element only three times.
Because the In and Not In operators do not support accessing values on record collections in the previous releases, the flow allots the account IDs to a collection of text , caAccountIds. The Get Records element retrieves all related account contact roles if their account IDs are in caAccountIds and if their Role matches Decision Maker.
The Get Records element fetches all related contacts if their contact IDs are in contactIDs. And by this way we can control the exceeding of the governor limit.
Previously, the Loop element iterated over a collection of values and retrieved all the related records. Each time the flow got an associated record via the Loop element, the flow used one SOQL query. If the flow got over 100 records, it failed because it exceeded the governor limit of 100 SOQL queries per transaction. If you debugged the flow, the debug details showed over 100 implementations of the Loop and Get Records elements.
Here are some more examples of using the new operators:
- Get a list of accounts in a list of mailing countries to display in a data table.
- Get a list of records using the Record ID Collection output of the newly intensified Lookup screen component.
- Get a products list from a custom action that outputs a collection of IDs from an external system.
🧿 Control Flow Screen Perceptibility Based On Dynamic Forms For Flow Picklist Values
You can now control a component’s visibility based on a Dynamic Forms for Flow picklist field (record field) on the flow screen. Previously, you could not add base conditional visibility using a Dynamic Forms for Flow picklist field on the flow screens.
For example, the below screen contains a Number Component called Age. Based on this field, the picklist field is put on view. If the Age is greater than 60, The Picklist Component Would you like medicare info? It depends upon the Age Component.
Whenever a user enters an Age value greater than 60, the picklist component is automatically displayed as shown in the above picture.
🧿 Two-Column Flow Layouts Are replaced by Multicolumn Screens
Two-column layouts are ignored. But your data isn’t high-flown, and a better layout option is available. With the Section component, you can set up record fields and screen components in up to four columns directly in the screen. To prepare for this change, recommend that you update your flow screens to use Section components.
Why we use :
- Each segment can have up to four columns, and you can modify the width of each column.
- Each screen can have multiple sections so that you can merge column configurations—some sections can use two columns while other sections can use four columns—all on the same screen.
- You can add section headers to provide context and let users collapse and increase size of each section.
- As you build your flow screen, you can see a live preview of the layout in Flow Builder canva.
- You can apply conditional visibility to an entire section so you can avoid arranging conditional visibility for individual screen components.
How to use : Determine whether your screen flows are distributed in a way that specifies a two-column layout. For example:
- You adjust the Layout property to Two Columns when you add a flow to a Lightning page, utility bar, or Experience Builder site.
🧿 Specify Offsets Time in Months for Scheduled Paths.
For each scheduled path on record-triggered flows, new offset options let you schedule the path to run on the same calendar day of next or another month. Previously, after you selected a time source for a scheduled path, you could define offsets only in days, hours, and minutes.
How to use:
When you add or edit a scheduled path, select Months After or Months Before to run the scheduled path on the same calendar day of next or another month.
In this Record-Triggered scheduled path, the source time is the flow-triggering event, and the schedule is offset to execute the path two months after the contact is created or updated.
🧿 Get Flow Elements Faster with Search
The Add Elements dialogue box in the Flow Builder canvas now incorporates a search bar.
In the Add Element dialogue box, search for the flow element to add by name of element or keyword as shown in the picture. For example, instead of searching for Action , search for a specific action type such as Send Email or Get Records.
