The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Winter 27 release brings Headless Toolkit, Multi Framework support, and Data SDK extensions (opens in a new tab)

Readers will learn how to build cross-framework applications on the platform using the new Headless Toolkit and understand how to extend the Data SDK with custom logic.

The Winter ’27 release, whose final rollout is set for October 9, 2026, centers on the Headless Toolkit. Salesforce capabilities are exposed as APIs, Model Context Protocol (MCP) tools and CLI commands that any authenticated caller can use. The Salesforce Development plugin for Claude Code adds Salesforce-specific skills, org context and recommendations for specialized plugins, and its skills also work with other coding agents. Multi-Framework apps now support Angular alongside React, with new templates, 2GP packaging and a Data SDK that can package custom logic as typed extensions. Beta microfrontends let an app run inside a Lightning page, with data passed down from the host component and events sent back up.

The Headless Experience Layer (Beta) lets a developer define a widget once and render it in Agentforce, Claude and Slackbot, linked through Apex, Lightning type and widget metadata. MCP now works in both directions, so Agentforce agents can be exposed as tools on custom MCP servers and AgentExchange MCP tools can be added to agents. The Marketing Cloud Engagement MCP server gains 40 tools. The CLI stops printing access tokens and secrets, with the temporary workaround ending October 28, 2026, and it adds async Apex templates and Scratch Org settings. API version 68.0 requires the Use Any API Auth permission for SOAP login from December 1, 2026, retires API versions 31.0 through 40.0, and adds a latest alias for REST URIs.

In Lightning Web Components, template expressions and LWC:external reach general availability, and state managers gain a refresh() method. Apex heap limits rise to 10 MB for synchronous and 25 MB for asynchronous transactions, and integration tests, FORMULA() and the Apex Symbol API are in preview or beta. Agentforce gains new Agent Script language features, file uploads in conversations, and generally available Multi-Agent Orchestration, along with simplified agent metadata types. Data 360 adds a context precision metric for retrievers and Python code extensions for zero-copy data. Web Console, a browser-based IDE, is generally available and needs no installation.

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

Worth reading?

Winter 27 release adds inline editing, sharing controls, email security, and report previews (opens in a new tab)

You will learn how to configure new Winter 27 capabilities that improve List View editing, preserve manual sharing during record transfers, streamline email domain verification, and enhance Lightning Reports and Dashboards.

The Salesforce Admins Blog has published a launchpad for the Winter ’27 release, which ships three times a year and is 600-plus pages of notes. The author urges admins to focus on the features that matter to their own org rather than reading everything. The post also explains that features move through pilot, beta and generally available (GA) stages, with beta features carrying limited support and best tested in a sandbox.

On the core platform, two new User Interface Settings let users inline-edit any field they can access, even if it is not on the page layout, and let List Views mix record types. Both are off by default. User field history tracking reaches GA, covering up to 20 fields on the User object and retaining history in the UI for 18 months. The standard Follow button can also be shown in the Dynamic Highlights Panel. For sharing, a setting now keeps manual shares when a record’s owner changes, and a forward-looking note says custom row causes for standard objects are targeted for October 10 through the Metadata API.

The security and email section covers a consolidated User Email Domains page in Setup, which shows verified and unverified address counts per domain. Admins can copy verified authorized domains from production into a new sandbox with one click, and set verification to Always, For Updated Addresses Only, or Never for each domain. Secondary sender addresses let sensitive emails route through Salesforce’s own Mail Transfer Agent. Experience Cloud Trusted URLs can now take individual Chrome extension IDs, with wildcards unsupported.

The Reports, Dashboards and Flow sections are the longest. Beta features include record previews in Lightning Reports, a Common Rows Only option for joined reports, and Lightning Reports and Dashboards embedded in LWR Experience Cloud sites. Flow Builder adds version Edit History with restore, element grouping, an Unused resource filter, Agent Action details in the canvas, and a User Context run option for flows using API version 68.0 or later. It also brings auto-generated element labels, persistent end elements, and save-time warnings for missing required fields and field length. Flows can now retry on record lock errors, Screen Flows can run as mass actions from List Views and Related Lists, and a native Time component is available. Beta Test Mode and mock outputs for Action and Subflow elements round out the testing tools.

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

Worth reading?

How Flow Tags simplify organization in the Automation App (opens in a new tab)

You will learn how to create tag categories, assign multiple tags to records, and filter your automation inventory using the dedicated Automation App interface.

Why read this

This approach replaces reliance on naming conventions and long Setup menus for faster flow management.

The Winter ’27 release introduces Flow Tags to help administrators manage rapidly growing automation inventories. This feature provides a flexible categorization method that moves beyond relying solely on flow names or folder structures.

Users must navigate to the Automation App to establish Tag Categories such as Business Area or Purpose. Once categories exist, administrators can add reusable tags and apply them to individual flows through row-level actions or directly within Flow Builder during the save process.

The primary value emerges when searching the platform. Administrators can display a Tags column in List Views, filter results by single or combined labels, and open any tag record to see a Related List of associated automations. This entire workflow operates exclusively within the Automation App and does not function from the standard Setup menu.

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

Worth reading?