1. Screen Styling

Provide a customized screen flow experience for your clients. Tailor many stylistic attributes for your screen flows, including background color, border color, border thickness, border radius, text color, buttons, and more elements. Any stylistic modifications you do supersede the default theme of your organization or Experience Cloud site.

You can put your own style based on your own branding on flow buttons including different states of these buttons like Default, Hover, Active. You can now change their bordre radius and border weight as well.

2. Build Record-Triggered Flow on Content Document and Content Version Object

As of Spring '26, you can now create record-triggered flows directly on ContentDocument and ContentVersion objects in Salesforce, facilitating automation for file uploads, updates, and deletions without depending exclusively on outdated platform event workarounds. This enhancement permits robust declarative governance, such as preventing file deletion or updating related records based on file metadata. This facilitates the automation of file-related tasks, guarantees compliance, and diminishes reliance on Apex for file automation.

3. LWR File Upload

The Spring '26 release introduces a native LWR File Upload component for Screen Flows, tailored for Experience Cloud sites (for both Authenticated and Guest Users). This enhancement improves file management within Flows by incorporating additional navigation and file naming options, building upon the existing lightning-file-upload LWC for LWR sites. This component facilitates advanced capability for managing file uploads in LWR settings, incorporating potentially new features such as mandatory characteristics, hence enhancing usability for developing file-centric procedures in customer-facing portals and communities.

With this new component, you can now list down only accepted file formats, whether to allow multiple file upload, File Field Name (Custom Field Name of Content Version object), Record Id (related to the files being uploaded), URL to navigate to after successful upload etc. 

4. Flow Debug Improvement

Maintain debug configurations upon saving modifications to your flow. Debug inputs, including triggered record values, debug options, and input variable values, now persist when you save modifications within your Flow Builder session. Refreshing your browser or closing Flow Builder resets all debug configurations.

5.Assign Flow Tests to Specific Flow Versions

When you have multiple flow versions, you can reuse tests from previous flow versions if the scenario still applies to a new version. Align flow tests precisely with each flow version so updates don’t cause incorrect results from other flow versions. Normally when we create new flow versions either we change the existing functionality or add new functionality. In that scenario, it might happen that your previous test might not work with the new flow versions. In that scenario, you need to make sure you create a new tests covering the new logic from the new flow version. This feature brings lots of fliexibility to the way flows are being tested today. 

Previously, a flow test applied only to the latest flow version. Starting in Spring ’26, you associate the same test with multiple flow versions. When you save a new flow version, the system automatically includes tests from the source flow version.

6. Kanban Board Screen Component

Following the Spring 26 release, the new Kanban Board component enables the display of records as cards within columns that signify workflow stages, eliminating the need for specialized Lightning implementations. Your users have immediate insight on record advancement and specifics without disrupting the workflow. The Kanban Board is in a read-only format, preventing users from moving cards between stages during runtime.

With this Kanban Board component, you will have the flexibility to configure the columns, how headers will be displayed (simple vs. path), perform grouping at column level, and also implement the summary field. On top of that, you can configure what will be displayed in the individual card, display in the footer etc.

I personally think this is a very powerful addition in Spring 26 release. Though this will only show the data in read-only mode, but I am quite sure in upcoming features, there will be interactivity within the Kanban board.

This is how all the opportunities will look like in Kanban Board grouped by "Opportunity Type" field and summarize the "Amount" field.

7. Flow Canvas Scrolling

The Salesforce Spring '26 release features enhanced navigation within the Flow Builder canvas. Users now possess various methods to navigate the Flow canvas, facilitating the management of extensive and intricate flows.

Supported Navigation Methods

• Trackpad scrolling
• Arrow keys
• Mouse wheel
• Scroll bars

8. Allow Collapsing Branching Elements

Enhance the efficiency of complex workflows by concealing superfluous details on the canvas. Flow Builder now enables the collapse and expansion of branching elements, including Wait, Decision, Loop, Path Experiment, and Async Actions, facilitating concentration on the essential components of your flow. Flow Builder retains your own settings for expansion and contraction to maintain a uniform workflow. This configuration is automatically and locally stored in your browser, facilitating a seamless return to your work without altering the view for other users.

9. View SubFlow Input & Output Variable Details

With Spring 26 Release, you will get the infobubbles for subflow output variables, which now display the custom description established by the administrator or developer. If a custom description is not specified, enhanced default text directs you to allocate a resource. Furthermore, see descriptions for a subflow's input resources in an infobubble, regardless of whether the resource is present. Previously, it was necessary to activate the input resource to ascertain its requirement.

10. Add Visually Distinct and Accessible Messages to Screen Flows

The new Message screen component allows you to incorporate a visually appealing, accessibility-compliant message on a screen to convey information, success, error, or warning notifications. Post-Spring 26, the Message display component can be incorporated into a flow screen. The message type dictates the color and icon employed for the message. Screen readers can convey the message type to users. You may input text or choose a flow resource to serve as the message.

11. Open Screen Flows in Lightning Experience with a URL

Initiate screen flows in Lightning Experience and Lightning console applications using a newly defined URL structure. Initiating flows in Lightning offers numerous advantages, including enhanced efficiency, retention of users within Lightning console applications, and a more uniform browsing experience. Information can also be transmitted into your flow via its URL.

To open a flow in Lightning Experience, append /lightning/flow/YourFlowNameHere to your URL. To run a specific flow version, append /lightning/flow/YourFlowNameHere/versionId to your URL.

To pass data into a flow through its URL, append ?flow__variableIdHere=value to the end of your URL. For example, to pass a case number into a flow, /lightning/flow/YourFlowNameHere?flow__variableIdHereID={!Case.CaseNumber}.

Use & to append multiple variables into a flow. For example, /lightning/flow/YourFlowNameHere?flow__varUserFirst={!$User.FirstName}&flow__varUserLast={!$User.LastName} passes both the user first name and last name into the flow.

12. Compare Screen Flow Versions

Utilize the Compare Versions functionality to automatically monitor alterations between any two versions of a screen flow. Examine modifications to screen flow elements, resources, fields, properties, components, and styles across flow versions.

In the Automation application for a screen flow, select the actions dropdown in the Flows list view, the flow's details page, or the versions page, and click on Compare Versions. Select the versions dropdown in Flow Builder, then click on Compare Versions. This option is accessible solely if the screen flow comprises two or more variants.

Choose the screen flow versions for comparison, then click Compare Versions. You may alter any flow version for comparison purposes. The comparative analysis reveals modifications to elements, resources, and flow attributes for the chosen screen flow versions. You may choose to display either only the modifications or all elements in the flow, irrespective of their change state. To display all items, uncheck Show Only Changed Items.

For more information about changes to an element, resource, or field click View Details. Review detailed changes to screen components, fields, flow properties, and component styles.

Final Thoughts

The Spring ’26 enhancements prove that Flow is no longer just "the engine under the hood"—it is now the primary architect of the user experience. By empowering admins and developers to control everything from granular component aesthetics to advanced execution monitoring, Salesforce has removed many of the traditional "glass ceilings" that previously forced teams toward custom code.

In next couple of days, I will bring more Spring 26 features here as well as my youtube channel. So it is highly recommended that you please subscribe to my channel and blog. Thank you!!

Disclaimer

This article is not endorsed by Salesforce, Google, or any other company in any way. I shared my knowledge on this topic in this blog post. Please always refer to Official Documentation for the latest information.

0 Comments