10 New Salesforce Flow Features in

Spring ‘25
1.Guide Users Through Screen Flows with Built-In Visual
Progress Indicators

Visually guide your users through the stages of your screen flows by using the built-in progress
indicator—no more writing custom code to create your own. Your users see which stage they’re on
and how many stages remain. Configure whether you want to show the progress indicator at the top
of the screen or in the footer. Pick from a simple-style or a path-style progress indicator. Path-style
progress indicators are supported only at the top of the screen.

Where: This change applies to Lightning Experience and Salesforce Classic (not available in all
orgs) in Professional, Enterprise, Performance, Unlimited, and Developer editions. It’s supported
only in Lightning runtime for flows. Built-in progress indicators are enabled by default for flows
created in Spring ’25 and later. For flows that were created in Winter ’25 or earlier, the built-in
progress indicators must be manually enabled. Built-in progress indicators aren’t supported in Field
Service Mobile or Salesforce Scheduler flows. The progress indicator settings are ignored when the
flow is implemented in an Actions & Recommendations component because the component already
displays the stages.

How: Progress indicators use stage variables to determine what stage the user is on. When a
screen loads, $Flow.CurrentStage is automatically updated to the stage that’s associated with
the screen, and the stage is added to the end of $Flow.ActiveStages if it isn’t an active stage
already. Create stage resources and define the stage label, order, and whether the stage is active by
default or not. Then, select the stage resource under the Stage field of the Screen element, or
assign the stage resources manually by using assignment elements.
Finally, to show a visual progress indicator, open the flow version properties. Then, select Show a
progress indicator on screen elements and then select the progress indicator type.
The user sees their progress on the page at runtime.

2. Send Emails with Attachments in Flow Builder

Enhance your Flow Builder emails by sharing documents or files with your recipients by using Send
Email action. To attach a file, provide the ID of a file to the Send Email action. The maximum size of
the email created, including attachments, is 35 MB.

Where: This change applies to Lightning Experience and Salesforce Classic (not available in all
orgs) in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.

How: In Flow Builder, in the element menu, search for and select Send Email. When you set input
values, turn on the Attachment ID field, and then add the ID of the attachment. The ID can be of a
Document, Content Version, or Attachment items. If you want to add more attachment IDs, enter
them as a comma-delimited list.
3.Create Flows with a New Streamlined Creation
Experience
We reorganized the flow creation window to help you create the automation you need quickly and
more efficiently. Flows are separated into four main categories, and you can filter and search to find
the automation you need.

Where: This change applies to Lightning Experience and Salesforce Classic in all editions.

How: To access the new flow creation experience, click New Flow from the Automation Lightning
app.

4.Generate a Detailed Description of a Flow with Einstein

Maintaining a flow can be challenging, especially if you didn’t create it. Without a detailed flow
description, it can be tough to figure out what the flow does. Now you can use Einstein to summarize
an existing flow or a new one as you create it. The summary describes all the flow steps and
includes the input and output variables, the objects that the flow changes, and the subflows that the
flow refers to. You can then add the generated summary to the flow description to keep everyone
informed.

Where:This change applies to Lightning Experience in Enterprise, Performance, and Unlimited

editions with the Einstein for Sales, Einstein for Service, or Einstein Platform add-on. Einstein
generative AI is available in Lightning Experience. To purchase the Einstein for Sales, Einstein for
Service, or Einstein Platform add-on, contact your Salesforce account executive.
How: Turn on Einstein generative AI in Setup. Next, from Setup, in the Quick Find Box, enter Flow
Creation with Einstein, and activate it. To summarize a flow, open it in Flow Builder. In the
Einstein panel, click Summarize Flow. The Einsten panel is open by default. If you don't see it, click

Einstein .

After you generate the summary, you can shorten or lengthen it (1). The standard summary provides
a high-level overview and includes the objects that were modified in the flow. The shorter version
summarizes the flow in one or two sentences.
You can then add the summary to the flow description (2). If your flow has an existing description,
you can update the description. Updating the description replaces the existing description with the
flow summary.

5. Create Responsive Screens with Automatically

Triggered Screen Actions (Beta)
You can now run autolaunched flows automatically in the background when the input values
associated with screen actions change. Previously, the only way to trigger a screen action was with
the click of a button by using the Action Button component. The output can be displayed on the
same screen, so your users can see the results of their actions on the same screen without clicking
any buttons.

Where: This change applies to both Lightning Experience and Salesforce Classic (not available in all
orgs) in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions. It’s
supported only in Lightning runtime for flows.

How: In Flow Builder, create an autolaunched flow that retrieves data and saves that data in output
variables. Activate the autolaunched flow. Then, create a screen flow and add a Screen element.
Next, add a screen action and select the autolaunched flow that you created. Configure the screen
action, and set input values. After that, add another component to the screen element that uses the
output of the autolaunched flow. To use the output from the autolaunched flow, in the screen
component’s input, select the autolaunched flow, then Results, and finally the output variable from
the autolaunched flow. You can see only the variables that were marked as Available for output.
Then, save and run the flow.

For example, suppose you want to automatically show all contacts for a selected account record.
Create an autolaunched flow that retrieves all contacts for an account. Activate the autolaunched
flow. Then, create a Screen flow and add a screen element to it. Add a Lookup component so that
users can select an account record. Add the activated autolaunched flow as a screen action and set
the input values. This way, the autolaunched flow runs when the input values for the Lookup
component change. Lastly, add a Data Table component, and add the Full Name, Email, and
Business Phone columns. The output of the autolaunched flow automatically populates the Data
Table when the lookup value changes.

At run time, when your user selects an account, they automatically see all the contacts for that
account on the same screen—no button clicks required.

6. Join Collections with the Transform Element

Combine source collections from related flow resources into one target collection. For example, you
can combine order records from an external system with Salesforce orders to get a combined data
structure that is displayed in a data table in a flow screen. The flow screen shows each order along
with the amount and the quantities.

Where: This change applies to Lightning Experience and Salesforce Classic in Essentials,
Professional, Enterprise, Unlimited, Performance, and Developer editions.

How: From Flow Builder, add the Transform element. Add two flow resources for the source
collections. Add a target collection that stores the combined data from the source collections.

Configure the join keys for each source collection, and select the join fields to return into the target
collection.
7. Enhance Flow Performance by Controlling the Number
of Records Retrieved with Get Records
When you work with large datasets, you can hit performance issues or governor limits if you use the
Get Records element to retrieve all records. If you set an upper limit to control data retrieval, you
improve ‌flow performance and reduce the risk of timeouts or errors. Use the All records, up to a
specified limit option to set an upper limit on the number of records to retrieve.

Where:This change applies to Lightning Experience and Salesforce Classic (not available in all
orgs) in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.

How: To set a limit on the number of records that the Get Records element retrieves, first add a Get
Records element to your flow. Then, under How Many Records to Store, select All Records, up to a
specified limit (1). Enter the maximum number of records to store (2). The Get Records element
retrieves all the records that meet the criteria up to the specified limit.
8. Flow and Process Run-Time Changes
Get new flow updates with these versioned changes.

Where: This change applies to Lightning Experience, Salesforce Classic, and all versions of the
mobile app in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.
These updates affect flows only if they're configured to run on API version 63.0 or later.
How: With versioned updates you can test and adopt run-time behavior changes for individual flows and
processes at your convenience. To change the run-time API version of a flow, open it in Flow Builder and
edit the flow version properties. To change the run-time API version of a process, open it in Process
Builder and edit its properties.

Clear a Reactive Data Table If the Source Collection Isn't Set

If a Data Table component's source collection is the output of a screen action, and the screen
action's autolaunched flow doesn't set a value for the output collection, the Data Table contents are
cleared. For example, let's say that a Data Table component is populated with records from a screen
action's output record collection. Then, the screen action is triggered again, but this time the output
record collection isn't assigned any records. The records that were in the Data Table from the first
time the screen action ran are now cleared from the Data Table. Previously, the records that were in
the Data Table from the first time the screen action ran would remain in the Data Table.

See Feedback from Screen Components with Invalid Values

Now your flow user can see whether an input value in a flow screen component is invalid when the
user changes the focus to outside the component. Previously, component validation error messages
appeared only when you moved to another screen or finished the flow.

Variables with Same Names in Parent and Referenced Flows Were Changed
Variables with the same API names in a referenced flow and parent flow no longer inherit values
from the parent flow. For example, a screen flow creates an account that assigns a value to the
group_type variable. The screen flow includes the Subflow element that executes a referenced flow.
The referenced flow also includes a group_type variable. The Decision element in the referenced
flow checks the value of the group_type variable that’s set in the referenced flow and not inherited
from the parent flow. The flow follows different outcome paths depending on the value of the
group_type variable.
9. Monitor All Failed and Paused Flow Interviews from the
Automation Lightning app
The new Monitor tab in the Automation Lightning app is your one-stop shop for finding all your failed
and paused flow interviews. The Monitor tab provides valuable data about why a flow interview
failed. Debug ‌failed flow interviews and resume paused flow interviews all from the Automation
Lightning app. Having the necessary information in one place helps ensure smooth and
uninterrupted business operations and improves overall efficiency and productivity.

Where:This change applies to Lightning Experience in Essentials, Professional, Enterprise,

Performance, Unlimited, and Developer editions.

How: If you’ve enabled access to the Automation Lightning app, the Monitor tab automatically
becomes available. View all the paused and failed flow interviews on the Monitor tab.
To debug a failed flow interview, on the Details page of the failed flow interview, click Open.

To resume a pause flow interview, on the Details page of the paused flow interview, click Resume.
10. Access Flow Versions in Flow Builder

Quickly manage different versions of a flow and view the status of each version in Flow Builder. To
see a flow’s versions, click the flow’s name in the Flow Builder navigation header. Clicking on a
different version opens that version in Flow Builder in a new browser tab.

Where: This change applies to Lightning Experience and Salesforce Classic in all editions.

How: To access different flow versions and see their statuses, click the name of the flow in the Flow
Builder navigation header.