These updates affect only flows that are configured to run on API version 64.0 and later.
Required Editions
| View supported editions. |
Use the Is Null Operator with Boolean Screen Components in Conditional Visibility Expressions
Now you can use the Is Null operator when referencing Checkbox and Toggle screen components in a conditional visibility expression. Previously, expressions with the Is Null operator didn’t identify when Boolean screen components were null. See Conditionally Show Screen Components.
Track Changes Between Flow Versions More Easily
With this versioned update, Salesforce sets location values to 0 in a flow XML file when the flow is saved in auto-layout. Previously, locationX and locationY fields were updated, and caused cluttered comparisons, making it hard to identify actual changes. Now, you can focus on real updates, enhancing productivity and code review efficiency.
For example, without this update, you add a new Decision element to a complex flow. When you save the flow in auto-layout, the change also triggers updates to the locationX and locationY fields for every element in the flow. The changes clutter the XML and obscure your actual changes. With this update, those fields are consistently set to 0, resulting in cleaner flow XML and more transparent version comparisons.
Repeater.AddedItems Collection Contains Empty Instances Even When Child Components Have No Selections
For flow screens created with API version 64.0 and later, when a child component such as a Lookup
component is added to a Repeater component, the Repeater.AddedItems output
collection contains an empty repeater instance. This Repeater.AddedItems
collection is not empty even if a user doesn’t make any selections from the child component
at run time because the Repeater component loads with an initial Repeater instance when the
user first accesses the screen. To determine if the Repeater.AddedItems
output collection contains any child component information, iterate through the
Repeater.AddedItems output collection and check the contents of the loop
variable using a Decision element with manually set conditions. If the value of
loop.lookUp.recordId (when the child component in the Repeater is a
Lookup) is null, then there’s no child component information, but rather an empty repeater
instance. Alternatively, make user input for the child component required to avoid an empty
repeater instance.
Screens Show Fields from Retrieved Custom Metadata and Custom Settings Records
In flows that run on API version 64.0 and later, a screen can show fields from custom metadata type records and custom setting records that a Get Records element retrieves. The screen shows these fields even when the running user doesn’t have access to them. Previously, in flows that run on API version 63.0 and earlier, the screen returned an error for those fields when the running user lacked access to them.
Flows can read public custom metadata types and custom settings regardless of the running user’s permissions, whether the flow runs in user context or system context. Because the Get Records element can retrieve the record, the screen can now use the fields that are available to the flow. Previously, the screen performed a second field access check and couldn’t resolve the fields.
