Many administrators approach Salesforce release notes like a January membership: strong intentions at the start, yet minimal follow-through later on. With daily task lists already filled with user requests and system fixes, reviewing hundreds of pages of documentation simply to locate the few updates that truly matter is rarely practical.
To save you time, this post bypasses the extensive Winter ’27 release notes. Instead, it highlights three notable Flow upgrades, such as repeatable Test Mode and bulk Screen Flows, that warrant setting aside an afternoon for hands-on review.
Following those updates, you will find a clear, dated schedule of the critical Spring ’27 security changes you should address before they disrupt connected tools or impact your team. Key claims link to their sources, and as always, verify everything in a sandbox before deploying it to your live organization.
Upgrade 1: Flow tags make automation easy to find
Picture a new teammate asking, “Which flows touch Opportunities?” and you answering, “Hang on, let me scroll.” Tags fix that.
You can attach one or more labels to a flow when you save it or add them later from the Automation app, and then filter your flow list by those labels.
The tool is simple, so the value is in the discipline. Before you tag anything, agree on three label families with your team:
- Ownership: who gets the call when it breaks (for example, team-sales-ops)
- Purpose: which business process it supports (lead-routing, renewals)
- Health: whether it needs attention (review-due, retire-soon)
Without that agreement, you will end up with Sales, sales and SalesTeam all coexisting, which brings back the folder chaos tags were meant to solve.
Upgrade 2: Flow Test Mode turns debug runs into reusable tests
For years, Debug has been a one-shot tool: set up your inputs, run, check the result, and repeat. Test Mode lets you save a test and replay it.
It is a beta, so you opt in first. Enable it under Setup > Process Automation Settings, then use the Test button inside Flow Builder. The builder then offers two views: Build for configuring the flow and Test for testing and debugging it.
The main change is that a test becomes an asset instead of a throwaway. You can store a scenario, run it again later and define the outcome you expect. After any edit, you replay the scenario and see whether something broke, much like a regression check for admins who don’t write Apex tests. Coverage is also tracked across saved scenarios that include an assertion.
Where to start:
- Pick the flow that would hurt most if it broke. It might be the one that assigns owners or sets renewal dates.
- Check what it supports. Test Mode is described as intended for record-triggered and autolaunched flows, so don’t plan on testing screen flows this way yet.
- Mock the risky elements. For an Action or Subflow element, open Test, select the element and choose Scenario Output, then Use Mock Output. You can then test your branching logic without sending a real email or making a real callout.
- Know the dependency. Mock outputs require Test Mode to be switched on first, and both are beta.
A rule for betas: use them to raise your confidence, but don’t make them the only gate before production.
Upgrade 3: Screen flows that run on many records at once
Until now, if users wanted to act on a batch of records, you either built workarounds or told them to click through each record. Now you can add a mass action to a list view or related list that launches a screen flow and passes it the IDs of every record the user selected.
A simple way to approach the build:
- Create the screen flow with a collection variable that accepts the incoming IDs. Salesforce’s own admin walkthrough names this resource “Ids.”
- Create a Flow Quick Action and place it on the list view or related list.
- For related lists, add a dynamic related list component to the record page in Lightning App Builder, as the same walkthrough describes.
- Stress test it. Try five records, then a few hundred, then include one record that will fail. Check record-count limits and failure behavior on a real list before you retire your current method.
One caution: some write-ups say the related list’s parent record ID is passed too, but Salesforce’s release note doesn’t explicitly confirm it. Until you have seen it work in your sandbox, don’t design around it.
Smaller Flow Builder improvements
- Earlier warnings. Flow Builder now flags a Create Records element with a missing required field, or a value likely to be too long, at save time.
- Collapsible sections. Group elements let you label parts of a canvas and fold them away, which helps on large flows.
- Save history. Flow Builder now shows a timeline of saves.
Full details are on the Salesforce Winter ’27 release page.
The Spring ’27 security countdown
This list is ordered by date, because that is how the changes will reach your org.
Start with the calendar. Spring ’27 production windows are currently listed as January 16, February 6 and February 20, 2027. Your instance has its own slot, so check the Maintenances tab on Salesforce Trust (status.salesforce.com). Treat dates as provisional: Salesforce sometimes postpones enforcement, adjusts scope or cancels a release update.
Before December 1, 2026
- Email verification exception. If a support case once turned off user email verification in your org, this needs action before December 1, 2026.
- SOAP API login(). New requirements start December 1, 2026, with sandbox and production deadlines after that and retirement later. List every integration that still uses it and plan its move to OAuth.
January 2027
- Sharing recalculation. Some recalculations are moving from real time to asynchronous, with enforcement in January 2027. This can break custom logic that assumes sharing updates instantly. Review flows that change ownership or sharing and then immediately depend on the result. There is no built-in test run for this, so build your own sandbox test.
- Installed packages. Ask each vendor whether their package is ready.
Spring ’27 and the February 20, 2027 deadline
- OAuth username-password flow. It retires on February 20, 2027, because credentials travel directly in the request. These failures tend to be silent, so search your connected apps and integration logs now. Confirm the date under Release Updates.
- User-agent flows. The OAuth user-agent flow and its hybrid version also retire in Spring ’27.
- Salesforce Connect cross-org adapter. Password and OAuth 2.0 authentication for this adapter are being retired.
- View Setup Audit Trail. At enforcement, the new permission is switched on automatically wherever View Setup already exists, but new profiles and permission sets need it granted explicitly. Decide who should see the audit trail.
- Guest users. Nearly every User field becomes hidden from guests by default. Browse your Experience Cloud site as a guest in a sandbox and note what disappears.
- Profile Filtering. Review flows, Apex and integrations that show profile names to anyone other than the running user, and grant the new permission to anyone who needs that visibility. Dates vary across sources, so confirm yours under Setup > Release Updates.
If you only have one day
Tag your flows, save one test scenario for your most important record-triggered flow, and search your org for anything logging in with a password. The first two make daily work easier. The last one protects you from a bad morning in February.
Need a Spring ’27 readiness check?
Ksolves is a Salesforce Summit Partner. Our Salesforce support and managed services team reviews orgs before each release: integrations still using password-based logins, flows that depend on real-time sharing, guest user exposure and package readiness. If an earlier release update has already broken something, our Salesforce Rescue team can stabilize the org first.
Talk to a Salesforce expert about a Spring ‘27 readiness review. For the previous cycle, see our Spring ‘26 release roundup.
Frequently asked questions
What is Flow Test Mode in Salesforce Winter ’27?
Flow Test Mode is a beta feature that combines debugging and testing in Flow Builder. You can save test scenarios, replay them after edits, set expected outcomes and mock Action or Subflow outputs. It is enabled under Setup > Process Automation Settings.
Can a Salesforce screen flow run on multiple records at once?
Yes. In Winter ’27, a mass action on a list view or related list can launch a screen flow and pass it the IDs of all selected records through a collection variable.
When does the OAuth username-password flow retire?
It is scheduled to retire on February 20, 2027, as part of Spring ’27. Check Setup > Release Updates in your org for the confirmed date.
What should Salesforce admins check before Spring ’27?
Prioritize integrations that use SOAP login() or the OAuth username-password and user-agent flows, flows that depend on immediate sharing recalculation, guest user access on Experience Cloud sites, installed package readiness and Setup Audit Trail permissions.
Do I need a Salesforce partner to prepare for Spring ‘27 security changes?
No. Most admins can prepare on their own. Start with Setup > Release Updates in your org, check the Maintenances tab on Salesforce Trust for your instance’s upgrade window, and test the changes in a sandbox. A partner becomes useful when your org has many integrations, custom packages, or complex sharing logic, or when your team doesn’t have the time or Salesforce skills to run those tests. In those cases, a readiness review can find the risks before enforcement dates hit. Ksolves offers that review, but a well-prepared internal team can complete the checklist without it.
![]()
5 MIN READ