Flow Builder: Platform Event–Triggered Flows, Record-Triggered Flows That Run After Save, More Debug Options, and System Context for Running Flows

Build platform event–triggered flows instead of event processes. Run record-triggered flows after each record is saved to the database. Debug scheduled flows, pass values into record variables, and roll back debug runs of autolaunched flows. Configure flows to run in system context without sharing.

Trigger a Flow to Run After a Record Is Saved
Creating or updating a record can now trigger a richer flow to run after that record is saved to the database. Previously, a record-triggered flow could only run before the record was saved, and the flow could only make updates to that new or updated record. After-save record-triggered flows can access other records, perform actions, and use more types of flow elements. These flows can even replace most workflow rules and record-change processes that are built in Process Builder.
Trigger a Flow to Run When a Platform Event Message Is Received
With platform event–triggered flows, you can do all your automation in one place. Previously, platform event–driven automation required you to use Process Builder and Flow Builder. Unlike event processes, platform event–triggered flows don’t require an associated Salesforce object and can access all available records.
Debug More Flows Faster
When you debug an autolaunched flow that saves changes to the database such as create records, you don’t have to revert those changes manually anymore. In Flow Builder, use rollback mode and let it save you the hassle. You can now use the debug option in Flow Builder for schedule-triggered flows. And the debug option includes the Lookup screen component so that you can set record variables more easily.
Create Flows with the Enhanced New Flow Window and Start Element
We streamlined the process for creating autolaunched flows with triggers. You now see the options to create a record-, schedule-, or platform event–triggered flow upon clicking New Flow in Setup. We also added trigger information and configuration options to the Start element in the canvas to make triggered flows easier than ever to build.
Configure Subflow Elements Without Assigning Output Values
When you add a Subflow element to a flow, we automatically store the output values. You’re no longer required to create and assign variables, but you can still opt to do so. This change doesn’t affect Subflow elements created before Summer ’20.
Configure Loop Elements Without Creating Loop Variables
When you add a Loop element to a flow, we create the loop variable for you. The loop variable temporarily stores the current item as the flow iterates over the collection variable's items. This change doesn’t affect Loop elements created before Summer ’20.
Take Some Tips from Guidance for Flow Builder
Get tips on how to improve your flows as you build them. Guidance for Flow Builder tells you, for example, that you forgot to close a loop. Or perhaps your flow invokes Apex code that uses the legacy Process.Plugin interface instead of the recommended @InvocableMethod annotation. You can show and hide these tips from the new Help Menu in Flow Builder.
Pass In the Record When Launching a Flow from a Lightning Page or a Quick Action
It’s now much easier to pass records into your flows. Each quick action automatically passes the record into the flow’s record variable named “recordId”. In Lightning App Builder, a simple checkbox lets the Lightning page pass the record into a record variable in the flow.
Access Nested Fields of Apex-Defined Data Types in Flows
Data access limitations for Apex-defined data types are removed, so now you can access nested fields of record and Apex-defined data types. For example, access {!MyApexClassOne.MyApexClassTwo.MyField} or {!MyApexClass.Account.BillingCity}. Previously, you were limited to a single level of field access for example {!MyApexClassTwo.MyField}.
Run Flows That Bypass User Permissions
Allow guest users to create or edit records they don’t have direct access to by setting your flow to run in system context without sharing. Flows running with this setting ignore object-level security, field-level security, org-wide default settings, role hierarchies, sharing rules, manual sharing, teams, and territories.
Updated Text Format Options for Text Template Flow Resource
Flow Builder now has updated menu option names for the Text Template flow resource for viewing text.
See Increased Screen Real Estate for Other Configuration Settings in Property Editors
Now your users can more easily see some configuration settings in property editors. We reduced the amount of space taken up by the Label, API Name, and Description fields when you edit an element or flow properties.
Let Flow Users Search for Records by Any Searchable Field
Now flow users can now search by any searchable field and choose from more than five records. Previously, the flow lookup component only supported instant search results. Users could search only by the name field, and the results were capped at five records.
Flow Builder Toolbar Improvements
Now flow users can view a flow’s version number, its active or inactive status, and the last modified time. The toolbar also shows hover text that gives the version number and flow status.

No matches found