Unanimous Flow Approvals – No More Workarounds

The Summer ’26 release is packing some serious Flow upgrades that move us closer to smoother automation. For the Flownatic community, this release represents a strategic shift: Salesforce is removing the roadblocks that have slowed us down, closing permission gaps, and allowing us to handle enterprise-grade complexity without the need for custom-coded workarounds.

In this post, we’re diving into two of the biggest wins for Flow Approvals this cycle: native unanimous consent for group approvals and expanded dependency visibility. Both are overdue fixes that change how we build compliance-ready automation.

Unanimous Consent

If you have ever had to build a compliance-heavy workflow that requires sign-off from an entire committee, you know the previous “administrative nightmare.” To ensure ten people all granted approval, admins were often forced to create ten separate, sequential approval steps: a maintenance disaster that was as fragile as it was tedious.

Summer ’26 introduces native unanimous consent for group approvals, turning what used to be a complex workaround into a single, elegant configuration. Here is the explanation of how these native mechanics operate:

• Individual Work Items: When a step is assigned to a group needing unanimous consent, every single member of that group receives their own unique work item in their queue.
• Approval Logic: The process is strictly gated by total agreement. The approval step only advances to the next stage if every member of the group grants their approval.
• Rejection Behavior: Accountability is immediate and efficient. A single rejection by any group member closes the step instantly. Most importantly, the system automatically withdraws all other pending work items for that group, effectively cleaning up user queues and preventing “zombie” work items from lingering.
• Security Guardrail: To maintain the integrity of the specific stakeholder group and ensure compliance, work items in these unanimous approval steps cannot be reassigned.

This is a massive architectural lever for those responsible for high-stakes data integrity, allowing us to build multi-stakeholder reviews without the bloat of previous releases.

Dependency Visibility

Historically, “god-mode” permissions have gated visibility into how your automation interacts with approval processes. Therefore, business analysts and process designers were flying blind. Summer ’26 lets teams see process logic without handing over admin access.

Previous Requirement: Previously, access to view flow dependencies within the Approvals app was restricted to users with the Manage Flow permission. This forced admins to give high-level, backend access to users who simply needed to understand process connections, creating a significant security risk.

New Requirement: Users with the Approval Designer permission can now view dependencies directly within the Approvals app.

This is a huge win for admins concerned with security. We can now empower our team members to understand the underlying logic and connections of their approval processes without handed out the keys to the entire Flow Builder backend.

Compatibility and Availability

Salesforce built these updates for the modern Lightning experience, and they’re available across all flagship editions.

Platform: These updates apply specifically to Lightning Experience.

Salesforce Editions:

• Enterprise
• Performance
• Unlimited
• Einstein 1
• Developer

Closing the Gap on Compliance

The updates to Flow Approvals in Summer ’26 are significant architectural improvements. Salesforce is eliminating the need for complex, manual workarounds that have historically crowded our orgs. These changes move us closer to a “no-code/low-code” enterprise reality where automation is both compliant and powerful. For admins who have spent years patching approval logic together, this release is a genuine exhale. And for organizations managing strict regulatory requirements, tighter permission scoping is a real compliance architecture upgrade.

As we march toward the Agentic Enterprise, these controls ensure that our frameworks remain scalable and secure. Now it’s time to put them to work. Head into your sandbox, pull up Flow Builder, and see how much simpler your next approval process can be. Happy building, Flownatics!

Explore related content:

Visual Comparison and Beyond – Flow Versions Just Got Easier

Supercharge Your Approvals with Salesforce Flow Approval Processes

Start Autolaunched Flow Approvals From A Button

11 Flow Updates in Summer 26 Release

Visual Comparison and Beyond – Flow Versions Just Got Easier

As we dive into the massive Salesforce Summer ’26 release, it is clear that the platform is delivering some serious automation upgrades. We have been watching a clear pattern for a few cycles now: Salesforce is steadily removing the friction points that have historically slowed admins down and is giving teams more control over how their automations behave. Today, we are focusing on one specific, highly anticipated quality-of-life win for Flow Builder that will change how you manage your automation versions: Visual Flow Version Comparison.

If you have ever taken over a flow mid-project, handed one off to a colleague, or simply tried to remember what you changed three weeks ago before hitting deploy, you already know the pain this feature is solving. In this article, we are breaking down exactly how Visual Flow Version Comparison works, what types of changes it surfaces, and why it is one of the most practical governance upgrades Salesforce has shipped in recent memory. Whether you are a solo admin trying to move faster or part of a team that needs tighter deployment controls, this feature has something for you.

What Are Flow Versions?

To truly understand the value of this new feature, we first need to talk about what flow versions are and how Salesforce handles automation architecture. In Salesforce, Flow Builder does not simply overwrite your active automation when you make a change. Instead, it utilizes a strict versioning system. Every time you open an existing flow, make adjustments, and click “Save As,” you create a new version of that flow.

This means a single flow can have dozens of versions, each capturing a snapshot of the automation’s logic at a specific point in time. However, only one version can be active at a time. This architecture is absolutely crucial for safe deployments and enterprise governance. It allows administrators to build and test new logic in a draft version while the older, active version continues to run uninterrupted in the production environment.

Furthermore, if a new deployment causes unexpected errors, this versioning system provides an immediate fallback mechanism, allowing admins to quickly deactivate the broken version and reactivate a previous, stable version.

The Old Way of Flow Version Comparison

Despite the benefits of having multiple versions, comparing them has historically been a nightmare for Salesforce administrators. Before the Summer ’26 release, if you took over a flow from another admin or simply forgot what you changed a month ago and needed to know the exact differences between Version 12 and Version 13, you had very few good options.

You generally had to open two browser tabs and manually click through every single node on the canvas, playing a tedious game of “spot the difference.” Alternatively, developers had to export the flow metadata and manually parse through raw, abstract XML files to find changes in the code. For a platform championing “low-code” and “no-code” solutions, this was a highly technical, time-consuming, and error-prone process. It often led to deployment risks when undocumented or accidental changes slipped through the cracks unnoticed.

The Summer ’26 Solution: Visual Flow Version Comparison

The Summer ’26 release completely revolutionizes flow management by solving this exact problem. Flow Builder now includes a visual comparison tool that allows you to identify flow version changes at a glance. Instead of relying on abstract tables or manually comparing complex XML files, admins can now visually identify differences side-by-side directly on the Flow Builder canvas. This tool improves overall readability and significantly reduces the risk of deployment errors by bringing transparency directly to the builder interface.

Types of Changes Highlighted

When you use the comparison tool, Flow Builder highlights modifications at a highly granular level, tracking everything from broad element changes down to specific configuration adjustments. When comparing versions, the interface will highlight elements and tag them with specific terms to indicate what happened:

Added: This indicates a brand-new element that exists in the newer version of the flow but was entirely absent in the older version being compared.

Updated: This status applies to elements that exist in both versions but have undergone configuration adjustments. The underlying logic, variable assignments, routing rules, or properties of the element have been altered between the two versions.

Removed: This highlights an element that was present in the older version but has been actively deleted or removed from the canvas in the newer version.

Changed Connector: Connector(s) are tied to different elements.

Compare Transform Element Changes

One of the most powerful aspects of this new visual tool is its deep integration with Transform elements. Data transformations can be incredibly complex, often containing dozens of individual field mappings. The Flow Version Comparison tool now provides a detailed breakdown of transform mappings, joins, and formulas.

If you modify complex data transformations, the tool makes it incredibly simple to easily identify any added, updated, or removed field mappings. You can review detailed configuration changes for complex transformations without having to manually inspect every single mapping line.

Supported Flows and Conditions

So, how do you access this new feature? The process is wonderfully straightforward and supported under standard Flow Builder conditions. To compare versions, you simply open a flow and navigate to the version dropdown menu at the top of the screen. From there, you select Compare Versions.

Once initiated, the tool provides flexibility in how you view the data. You can switch seamlessly between a table view (for a list-based breakdown) and the visual canvas view. To dive deeper into a specific modification, simply click an element with changes to get more granular details and see exactly what configuration adjustments were made.

Supported Licenses and Availability

Salesforce has made sure this highly anticipated feature is widely available to the ecosystem, not just restricted to premium tiers. The Visual Flow Version Comparison tool applies to both Lightning Experience and Salesforce Classic. It is available across a comprehensive range of licenses, specifically in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions. Whether you are a solo admin in a small business or part of a massive enterprise deployment team, you will have access to these critical visibility tools to keep your automations safe and predictable.

The Automation Visibility You’ve Been Waiting For

The ability to visually compare flow versions is exactly the kind of quality-of-life win that Flownatics have been asking for. No more tab-switching, no more XML spelunking, no more hoping you remember what you changed three weeks ago.

For admins managing complex orgs, this feature is a genuine risk reducer. Deployment reviews get faster. Handoffs between team members get cleaner. Audits stop being a scramble. And for any admin who has ever activated a flow and immediately wondered what actually changed since the last version, this is the answer.

Salesforce is taking the no-code and low-code automation story seriously at the enterprise level, and Visual Flow Version Comparison is proof that robust lifecycle management tooling is no longer reserved for developers. It belongs in the builder interface, and now it finally is. If you are not already reviewing your most critical flows and documenting version histories, Summer ’26 is the perfect time to start. This tool makes it easier than ever to build that habit.

Explore related content:

11 Flow Updates in Summer 26 Release

Open a Page Action: Redirect Users After a Screen Flow

Choices, Choices: What Are Radio Button Groups Best Used For

Warn and Inform with Native Toast Messages in Salesforce Flow

Open a Page Action: Redirect Users After a Screen Flow

For years, Salesforce administrators and developers building Screen Flows have run into a familiar, frustrating wall: the post-flow navigation gap.

Picture this scenario: Your user opens a flow on an Account record. They carefully fill out a series of screens to log an issue or create a related record, clicks “Finish,” and then… nothing. They are left sitting exactly where they started. To see their work or continue their task, they are forced to manually scroll down to a related list, hit refresh, or use global search to find the record they literally just spent two minutes creating.

How Admins Can Solve Screen Flow Navigation Issues

The ecosystem relied on custom Aura components, LWCs, or unofficial open-source extensions like UnofficialSF. These handled simple browser redirects but came with real tradeoffs. Code maintenance, package dependencies, and unnecessary complexity piled up fast. What should have been a standard declarative process required custom development instead.

With Salesforce’s introduction of the native Open a Page core action, that workaround era is officially over. You can now dynamically launch Salesforce records or any external URL directly from your flow, seamlessly bridging screen transitions or gracefully redirecting users upon flow completion. Let’s dive deep into how this feature works, its availability, and step-by-step instructions on implementing it using a real-world, high-impact use case.

Use Case: Instant Case Redirection from an Account Page

Instead of forcing the agent to hunt for the new case in the related lists, we will use a Screen Flow that captures the context, creates the Case record, and uses the Open a Page action to automatically pop open the newly created Case record in a clean browser window or tab upon completion.

Flow Configuration

As visualized in our Flow Builder layout, the architecture of this solution is exceptionally clean and entirely declarative, requiring only five steps from start to finish:

Why it works: The action executes directly within the flow transaction and acts as the ultimate user-friendly transition point. The user experiences a logical, smooth progression from gathering details to reviewing the finalized record.

How to Configure the “Open a Page” Action Step-by-Step

Setting up the action inside your Flow properties panel requires minimal configuration but yields incredible utility. Once you drag a new Action element onto your canvas or click the plus sign below your Create Records element, search for and select Open a Page. Fill out the parameters as follows:

• Label: Open Page (or a highly descriptive name like “Redirect to New Case”)

• API Name: Open_Page

• Page Type: Select Salesforce Record Page from the dropdown. (Note: You can also choose External Page for arbitrary web URLs).

• Record ID: Bind this dynamically to your case creation variable: {!CaseRecordVar.Id}

• Object Name: Type or select Case to tell the framework which layout style to load.

• View Mode: Select the radio button for View (loads the standard record detail view) or Edit (pops open the record in edit mode). For this use case, choose View.

• Where to Open the Page: Select New Browser Window to open the record in an independent tab, keeping the original Account window pristine and undisturbed. Our tests for this use case showed that all options produced the same result opening the case on a new browser tab and changing the focus of the browser to the case (tested on MacOS using Chrome).

Availability & Deployment Scope

This enhancement isn’t locked behind premium tiering. Salesforce has made it widely available across the platform ecosystem to immediately improve user experiences:

• Environments: This change applies fully to both modern Lightning Experience and classic desktop layouts (Salesforce Classic).

• Editions: Supported across a massive suite of tiers, including Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.

Pro-Tips for Salesforce Admins

Use Stored Record Id: If you use a record variable to create the record, your brand new Id will be populated in the record variable. For all other methods you can refer to the create step to use the new Id.

Leverage External URL Redirection: Don’t limit your thinking entirely to standard Salesforce records! By switching the Page Type parameter to an external configuration, you can dynamically pass parameters via a query string. This launches third-party legacy ERPs, internal document management portals, or customized external tracking systems right inside your flow sequence.

Don’t Over-Rely On “Where to Open the Page”: OS and browser settings often dictate what happens next. Your outcome may not match what is listed as a choice in the pulldown.

Why Better Flow Navigation Drives Salesforce User Adoption

Small friction reductions transform a CRM into a platform users actually enjoy. For years, the post-flow navigation gap was a persistent pain point for admins. The common fix involved Aura components, LWCs, and community-built extensions. These workarounds got the job done, but they were never the right long-term answer.

The Open a Page action delivers a seamless experience with zero custom code. Use it to redirect users to a new record, launch an external portal, or guide next steps. The use case we walked through is just one of dozens of high-impact scenarios where this action can eliminate confusion and keep your users moving forward.

Let me know, if you plan on using this action: Where will you use it?

Explore related content:

11 Flow Updates in Summer 26 Release

Choices, Choices: What Are Radio Button Groups Best Used For

Field Access Summary

How to Create, Customize, and Share List Views in Salesforce

Salesforce admins, devs, consultants: stop hunting for field API names.

Salesforce Field Scanner is a one-click browser tool that scrapes every field, label, API name, and value from the current Salesforce page and exports clean JSON. Use it for reports, automation, API work, or piping data into an LLM.

Try it: https://apaops-storefront.pages.dev/products/salesforce-field-scanner-640498/

#Salesforce #SalesforceAdmin #SalesforceDev