The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Must-read

Flow Test Mode adds saved Test Scenarios, assertions and mock outputs to Flow Builder (opens in a new tab)

You will learn how to create and save Flow test scenarios, add assertions and mock external action outputs, and why these tests are not yet enforced at deployment.

Why read this

The piece also notes that FlowTest is a separate metadata type to include when deploying.

  1. Save Test Scenario with inputs
  2. Enable Automated Test Scenario
  3. Add assertions and mock outputs
  4. Run All for coverage and results
How a saved Test Scenario runs automatically with assertions

Salesforce’s Winter ’27 release introduced Flow Test Mode, a dedicated testing canvas for Autolaunched and Record-Triggered Flows that is currently in beta. It is enabled through the Process Automation Settings page in Setup, and the author recommends trying it in a sandbox first. Within the new canvas, builders can debug by record Id or name, test primitive collection variables by separating values with semicolons, and save reusable Test Scenarios with labels, descriptions and run options such as rollback mode. Scenarios can be run manually or set to automatic, with assertions checking expected results, such as whether an element was visited or a field has a given value, and with the choice of which flow versions to test. Mock outputs let builders supply fabricated responses for external action elements, so tests can run without calling the endpoint and can force success or fault paths.

The author highlights practical uses: rerunning a scenario that reproduces a bug until it is fixed, using saved assertions for regression testing after org changes while watching coverage and results, and testing integrations without configuring live connections. He also explains deployment: FlowTest is its own metadata type, separate from the flow, so tests must be packaged and deployed individually. Currently a flow can be deployed without its tests, making them a nice-to-have rather than an enforced requirement as Apex tests are, and the author hopes enforcement will come once the feature reaches general availability.

The piece concludes that Flow Test Mode still falls well short of Apex testing, which requires at least 75% coverage before production deployment and cannot be bypassed, while flows can currently be built directly in production. Mock outputs are a point-and-click analogue of Apex’s HttpCalloutMock approach, and the Test Discovery API can run Apex and flow tests together. Overall, the author sees the feature as a significant and promising step for Flow, though it is still in beta.

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

Worth reading?

Salesforce Health Insights scans an org and ranks what to fix first (opens in a new tab)

You will learn what Salesforce Health Insights does, its two pillars of Product Adoption and Implementation Health, and who can access it in the Winter '27 release.

Why read this

The piece stays at the level of an overview and does not explain how to configure it.

  1. Scan org configuration and usage
  2. Evaluate against benchmarks
  3. Rank findings by severity
  4. Deliver next best actions
How Salesforce Health Insights turns an org scan into next actions

Salesforce Health Insights is a Salesforce-native solution that scans an org, evaluates it against benchmarks, and turns the findings into prioritized next best actions. The article presents it as a way to replace a manual org health review, which it says can take up to three weeks, with an on-demand scan that returns ranked results in near real time. The recommendations are built from the org’s own configuration, feature set and usage patterns, and ranked by criticality and the effort needed to fix them.

The tool has two pillars. Product Adoption shows which licensed capabilities are owned, which are used, and where there is room to grow, including license utilization over the past 30 days. Implementation Health delivers severity-ranked insights across Security and Process Automation, with recommendations meant to reduce exposure and prevent automation failures. The article also describes a headless delivery model, with a conversational view inside Salesforce and access through Slackbot outside it.

According to the article, Salesforce Health Insights is available with the Winter ’27 release for Signature Success Plan customers on Core products at no extra cost, and is found by searching for it in the App Launcher. The piece is a product announcement written by Salesforce and gives no detailed configuration steps or measured results.

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

Worth reading?

Using latest for the REST API trades upgrade control for convenience (opens in a new tab)

You will learn what the latest alias for REST API versions changes, why it shifts upgrade timing onto your release testing, and why even fixed versions still depend on the current platform.

Fixed version

  • Upgrade is a planned event
  • Testing happens before the switch
  • Still runs on current platform

latest alias

  • Upgrade arrives with the release
  • No action needed to adopt it
  • Testing moves to release preview
Fixed versions and latest differ in who decides when an upgrade happens

Winter ’27 lets integrations target the REST API with the alias latest in place of an explicit version number such as v68.0. The alias removes the need to update integration versions every four months and spares you from tracking version retirements, since requests always reach the current release.

The author argues the convenience comes at a cost of control. An integration on latest picks up whatever Salesforce treats as current, so when the next version arrives, behavioral differences, new fields or updated metadata can reach your code without a planned upgrade. Salesforce recommends fixed versions for production integrations with a specific contract and latest for scripts and internal tools.

The post also points out that a fixed version does not fully protect you. Once a new version goes live, requests to older fixed versions are served by the current platform with backward compatibility applied, so the platform underneath you still changes. The author concludes that non-critical work can use latest, while critical integrations should stay on fixed versions and be regression tested every release.

Read the original at Bob Buzzard Blog (opens in a new tab)

Worth reading?

New Collection Filter Criteria Resource simplifies Flow Builder data manipulation (opens in a new tab)

You will learn how the new Collection Filter Criteria Resource moves collection filtering out of the Flow canvas and into reusable resources.

Why read this

The piece explains how this change reduces visual clutter, optimizes governor limits, and enables in-memory sorting and filtering.

Collection Filter Criteria

  • Configured via Manager tab
  • Returns only first match
  • Eliminates extra Loop steps
  • Supports child relationships

Collection Filter and Sort

  • Placed directly on canvas
  • Returns full record collection
  • Requires additional Loop steps
  • Standard element configuration
Comparison of the new Collection Filter Criteria resource against existing Flow elements

Introduces the Collection Filter Criteria Resource as a Winter ’27 preview feature that shifts collection filtering from canvas elements to the resource manager. It replaces the traditional Collection Filter node, allowing administrators to define dynamic filter conditions and sort orders directly in memory without triggering additional SOQL queries or DML operations.

Explains the practical benefits, including cleaner Flow Builder canvases and optimized transaction limits. Multiple distinct filter views can now point to a single source collection, eliminating sequential logic and reducing visual complexity while speeding up execution across screen and autolaunched flows.

Covers advanced integration with Apex defined variables, noting that future updates will allow filtering based on child relationships within custom data structures. This capability aims to remove unnecessary loops during collection processing and hints at upcoming list and map functionality resembling native Apex collections.

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

Also told by Salesforce Admins Blog (opens in a new tab), Salesforce Time (opens in a new tab)

Worth reading?

Must-read

Winter '27 lets admins trigger Screen Flows from List Views and Related Lists (opens in a new tab)

A step-by-step setup for the Winter '27 feature that passes the records a user selects in a List View or Related List into a Screen Flow.

  1. Build Screen Flow with ids variable
  2. Create Flow action on the object
  3. Add to List View Button Layout
  4. Add to Dynamic Related List – Single
Setup for running a Screen Flow on selected records

Starting in Winter ’27, users can select several records in a List View or a Related List and hand them to a Screen Flow that opens in a modal. The article treats it as an overlooked part of a large release because it lets admins build mass actions without code.

The setup has one detail that is easy to miss. The flow needs a text collection variable named ids, in lowercase, marked as available for input. The selected record Ids arrive in that variable. The example flow gets the matching Contacts, shows them in an editable Data Table on a screen, and writes the edits back with an Update Records element, with fault paths on the data elements.

To expose it, create an action of type Flow on the object and add it to the List View Button Layout under the Lightning Experience List View actions. For Related Lists, create the same kind of action, then add it to a Dynamic Related List – Single component on the parent’s Lightning Record Page.

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

Worth reading?