The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Salesforce Winter '27 brings Flow testing, bulk screen actions, and higher heap limits (opens in a new tab)

Readers will learn how to implement the new Flow Test Mode, process multiple records via List Views, and adjust to increased Apex heap limits and updated REST API versioning without manual tracking.

The release introduces Test Mode for Flow Builder, enabling repeatable testing with assertions and mock outputs for external callouts. Screen Flows launched from List Views or Related Lists can now process multiple selected records by accepting a lowercase ids collection variable. Reactive Formulas allow Conditional Visibility to evaluate same-screen inputs instantly, while new save-time validation catches missing Required Fields and character limit breaches before runtime.

Logic handling gains Split by Field Value and Split by Date elements, which create automatic branches but do not fully replace Decision elements. Navigation improves through an Unused Resources filter, Element Grouping, and an Edit History panel. Security receives a User Context option that enforces running user permissions, and an org-wide toggle preserves Manual Shares when record ownership changes.

Synchronous Apex transactions now support a 10 megabyte heap limit, while asynchronous transactions reach 25 megabytes, with a transition setting available to manage the shift. List View inline editing expands to include off-page layout fields and mixed Record Types. Integrations may use latest for REST API versioning, and Field History Tracking becomes generally available for the User object.

Read the original at Salesforce Ben (opens in a new tab)

Also told by Salesforce Ben on YouTube (opens in a new tab)

Worth reading?

Must-read

Salesforce introduces beta Test Mode for Flow debugging and regression testing (opens in a new tab)

You will learn how to enable and use the new Test Mode beta to save, reuse, and automate Flow validation without leaving the builder.

Why read this

You will also understand upcoming capabilities like element mocking, test coverage tracking, and Agentforce powered troubleshooting.

Traditional Approach

  • Debug button only for troubleshooting
  • Testing and debugging require separate actions
  • Manual checks lack reusable configurations
  • Cluttered design canvas during validation

Test Mode Workspace

  • Dedicated view replaces Debug button
  • Merges debugging and automated testing
  • Saves runs as reusable manual test scenarios
  • Converts manual tests to regression tests with assertions
How Test Mode consolidates Flow debugging and automated testing

Salesforce has released a beta version of Test Mode, a dedicated workspace that replaces the traditional Debug button in Flow Builder. This update merges debugging and automated testing into a single interface, requiring administrators to enable the feature through Process Automation Settings before it becomes available for Record-triggered and autolaunched flows.

The new workspace allows builders to save execution runs as reusable manual test scenarios. These saved configurations preserve triggering records, input variables, and mocked outputs. Administrators can now supply static record identifiers for poorly searchable objects and populate primitive collections directly in the test panel. Once validated, these manual scenarios can be transformed into permanent regression tests by attaching expected results.

Test Mode also introduces element mocking, which simulates outputs for subflows and external actions to keep testing isolated from live endpoints. The roadmap includes Winter ’27 enhancements such as visual test coverage tracking on the canvas and Agentforce powered capabilities. These future features will synthesize transaction context to diagnose cross automation failures and automatically generate comprehensive test scenarios with isolated data silos.

Read the original at Salesforce Admins Blog (opens in a new tab)

Worth reading?