Salesforce Winter '27 for Admins: Flow Test Mode, List Views and the Setup Changes Worth Your Time

Winter '27 is a housekeeping release for admins. The headline, Flow Test Mode (Beta), is opt-in and does not retire the debugger. Several useful changes, including inline list-view editing and keeping manual shares, are off by default. One enforced release update, Profile Filtering, can change what your automation sees.

Is Flow Test Mode worth switching on?

Yes, in a sandbox first. Flow Test Mode (Beta) is off until you select it under Process Automation Settings in Setup. Per the Winter '27 release notes it applies to Lightning Experience in Professional, Enterprise, Performance, Unlimited and Developer editions, for record-triggered and autolaunched flows. It is a Beta under the Beta Services Terms, and the notes do not retire the existing debugger; debugging and saved scenarios now live in one place.

• Reusable scenarios with assertions that report pass or fail on every run.
• Mock outputs for Action and Subflow elements, so a callout or Apex action returns a canned response instead of hitting a live system.
• A record ID field in the debug panel for 15- or 18-character IDs. This page's Where line omits Professional.
• Primitive collection inputs for text and number collections; record collections were dropped the week of 24 August 2026.
• Agentforce-generated scenarios from the Agentforce Vibes terminal need the Agentforce Platform Developer and Admin permission set licence per the Who line, so they are a paid extra.

What makes flows easier to maintain?

Feature	Editions per the Where line (as at September 2026)	On by default?	Why you care
Flow Tags	Professional, Enterprise, Performance, Unlimited, Developer	No setting	Bulk-tag flows in the Automation App
Edit History	Enterprise, Performance, Unlimited, Developer	No setting	Save-by-save diffs; restore any past save
Group elements	Essentials, Professional, Enterprise, Performance, Unlimited, Developer	Rolling from Winter '27	Collapsible groups; auto-layout only
Unused Resources filter	Essentials, Professional, Enterprise, Performance, Unlimited, Developer	No setting	Lists unused resources; auto-layout only
Version comparison	Professional, Enterprise, Performance, Unlimited, Developer	No setting	Element names open a change panel
Denser canvas	Essentials, Professional, Enterprise, Performance, Unlimited, Developer	Automatic	Smaller cards; End element becomes an icon
Cosmos theme	Essentials, Professional, Enterprise, Performance, Unlimited, Developer	Automatic	Follows the org theme; no dark mode
Keyboard shortcuts	Starter Suite, Pro Suite, Essentials, Enterprise, Performance, Unlimited, Developer	No setting	Arrow keys, cut, copy, paste, Ctrl+K or Cmd+K for the Toolbox
Split by Date or Field Value	Essentials, Professional, Enterprise, Performance, Unlimited, Developer	No setting	Aimed at marketers; confirm on a record-triggered flow
Decision navigation	Essentials, Professional, Enterprise, Performance, Unlimited, Developer	No setting	Click a path to see its conditions; rename inline

Which Flow behaviour changes could surprise you?

User context now enforces permissions. The new User Context–Enforces User Permissions run option stops a screen or autolaunched flow inheriting elevated permissions from a system-context caller. It applies only to flows on API version 68.0 or later, and the API 68.0 run-time changes page lists nothing else, so existing flows keep their behaviour until you change their version.

Record-lock retry. A flow that hits UNABLE_TO_LOCK_ROW during transaction initialisation now waits 10 seconds and tries once more. No setup; Essentials through Developer.

Field length and required field warnings at save time. Flow Builder now warns when an Assignment sets a fixed text value longer than its field, or a Create Records element using a record variable skips a required field. Warnings only: the flow still saves. Professional and above.

Screen flows. A Flow-type quick action on a list view or related list now receives the selected record IDs as a mass action (Professional and above). Screens gain a native Time component and visibility rules that react to same-screen formulas; both Where lines omit Professional.

What was pulled. The Automation change log records Reduce Limit Failures in Scheduled Flows with Dynamic Batch Sizing as removed the week of 24 August 2026: "This feature isn't quite ready yet, so we removed it for now." The Flow Error Handling page's introduction still mentions it, but no feature page exists.

What changes for approvals?

All three list Enterprise, Performance, Unlimited, Einstein 1 Editions, Agentforce 1 Editions and Developer. The Request Approvals component in Lightning App Builder offers submitters up to 10 autolaunched flow approval processes on one record page. The Orchestration Work Guide can open the next work item automatically, off by default. And deleting a parent record now cancels its in-progress approval submissions so they can be deleted, which helps with privacy deletion requests; you need Approval Admin or Modify All Data.

What is new in Setup and list views?

Inline editing in list views. Two new User Interface Settings, both optional and off by default: Remove list view inline edit dependencies on page layout, and Make inline edits in list views with multiple record types. Professional and above. Review field-level security before flipping the first one.

Keep manual shares when transferring records. One Sharing Settings toggle, off by default; previously an owner change deleted the manual shares. Professional and above.

User field history tracking, now generally available. Track up to 20 fields on the User object, including changes made through Apex or the API. Enterprise and above.

Lightning App Builder. Page-based quick actions (Beta) reuse one quick action page across actions, from September 2026 per the When line. Picklist visibility rules gain Is Blank and Is Not Blank. The Follow button can show on the Dynamic Highlights Panel, hidden by default. All three list Group through Developer.

Advisements (Beta) now flags up to 21 potential implementation risks, up from 14, but needs a Signature Success plan on Enterprise, Performance or Unlimited, production orgs only.

Setup with Agentforce has no Winter '27 release note; the only official source is the Salesforce Admins blog post of 26 May 2026, which says Setup actions do not consume Agentforce credits.

Release updates are post 1's job. In short: Profile Filtering, first available in Summer '26 and enforced in Winter '27, hides other users' profile names unless the viewer holds View All Profiles, so check any flow or validation rule that reads one. Three accessibility release updates (page headers and modals above 200% zoom, cards and panels, date pickers and popovers) are also enforced. Two items in our July post have moved since: Authorized Email Domains was cancelled (replaced by Maintain Your Email Verification Exception, due 1 December 2026) and the username-password OAuth retirement moved to 20 February 2027.

What happens with Agentforce being on by default?

Per the Agentforce Platform Enabled by Default note, this applies to Enterprise, Performance, Unlimited and Developer editions with Foundations or Agentforce 1 Editions. New Winter '27 orgs have it on; existing orgs are enabled on a rolling basis from the first week of September, and the setting itself is planned for removal later in Winter '27. On cost: "The platform is enabled at no additional cost and there are no changes to billing." Admins get Agentforce Builder if Einstein generative AI is on; other users need the Manage AI Agents permission. The off switch is the Einstein setting in Setup.

The Help Agent also appears behind the ? icon with no setup, in English, for Free Suite, Starter Suite, Pro Suite, Professional and Enterprise (Enterprise rolling from August 2026; Performance and Unlimited are not listed). Tell the team both are expected and nothing has been bought.

Where are reports and dashboards?

Three items, all Beta. Record previews: opt in under Reports and Dashboards Settings, then an eye icon opens record links in a side panel; Enterprise and above. Dashboards and reports can be embedded in LWR Experience Cloud sites (Professional, Enterprise and Unlimited); the report component needs a Support case.

What should a solo admin do this month?

1. Confirm your date. Every Australian-hosted production instance (AUS58 through AUS102) upgrades on Saturday 10 October UTC per Trust data as at September 2026 (for New Zealand readers, 04:00 to 08:30 NZDT on Sunday 11 October); check your own instance.
2. Use the preview sandbox if you have one. Only a sandbox created or refreshed before 6:00 PM PT on 27 August (13:00 NZST, Friday 28 August) is on Winter '27 now; others upgrade on 9 or 10 October, so book testing after the October window.
3. Open Setup → Release Updates. Confirm Profile Filtering and search flows and validation rules for profile-name references.
4. Turn on Flow Test Mode (Beta) in the sandbox and write one scenario with assertions per record-triggered flow.
5. Tag and tidy. Tag flows in bulk from the Automation App and run the Unused filter.
6. Decide the three toggles: the two inline-edit settings and Keep manual shares.
7. Leave flow API versions alone until you have tested the user-context change on a copy.
8. Brief the team on Help Agent and Agentforce Builder appearing.

If nobody has the hours, a fractional Salesforce admin from SAASKOOL does this (from NZ$99/hr) and managed services (from NZ$1,000/month) include release readiness; see when a fractional admin makes sense and our Summer '26 write-up.

Frequently Asked Questions

Is Flow Test Mode available in Professional Edition? Yes for the core Test Mode and mock outputs: per the Winter '27 release notes both apply to Professional, Enterprise, Performance, Unlimited and Developer editions once you enable Flow Test Mode (Beta) in Process Automation Settings. The record ID and primitive collection pages omit Professional from their Where lines, so check the capability you need.

Does Winter '27 change how my existing flows run? Mostly no. The one versioned change, the User Context–Enforces User Permissions option, applies only to flows on API version 68.0 or later, so a flow on an earlier version keeps its behaviour until you change it. Two changes apply everywhere without setup: the 10-second record-lock retry, and save-time warnings for oversized fixed text values and missing required fields.

Was dynamic batch sizing for scheduled flows removed from Winter '27? Yes. The Automation section change log records Reduce Limit Failures in Scheduled Flows with Dynamic Batch Sizing as removed the week of 24 August 2026, with a note that the feature was not quite ready. The Flow Error Handling page introduction still mentions it, but no feature page exists, so do not plan around it.

Will Agentforce being enabled by default cost my business anything? Not according to the release note, which says the platform is enabled at no additional cost and there are no changes to billing. It applies to Enterprise, Performance, Unlimited and Developer editions with Foundations or Agentforce 1 Editions, rolling out to existing orgs from the first week of September 2026. To turn it off, disable the Einstein setting in Setup.

When does Winter '27 reach Australian-hosted orgs? Per the Salesforce Trust maintenance data as at September 2026, every Australian-hosted production instance (AUS58 through AUS102) is scheduled between 04:00 and 08:30 NZDT on Sunday 11 October 2026. Preview sandboxes were upgraded on 28 and 29 August; non-preview sandboxes upgrade on 9 and 10 October. Confirm your own instance on Trust.

---

Release readiness is standing work in SAASKOOL managed services; a fractional Salesforce admin can run the checklist above as a one-off. Start with the free health check.