Today4 stories

The Daily Org

Spring '27Sandboxes 6 Feb 2027

Curated by Abhinav (opens in a new tab)

Vol. I · No. 3The independent daily for Salesforce admins, developers and architects4 stories

Must-readArchitecture

Winter ’27 release guides architects through security enforcement and agent scaling (opens in a new tab)

You will learn which authentication methods retire by early 2027 and how to migrate integrations to secure alternatives.

Why read this

The piece also outlines updated platform limits, new Agentforce orchestration patterns, and governance tools that shape long-term org architecture.

Winter ’27 Release

  • Mandatory security enforcements
  • Capacity and automation updates
  • Agentic architecture design
  • Governance and observability
The Winter ’27 release guides architects through four key architectural focus areas

The Winter ’27 guide presents the release as a set of coordinated architecture decisions across security, capacity, agentic design and governance. It recommends starting with operational risk, then judging whether new platform capabilities help existing configurations scale and fit the longer-term architecture roadmap.

The security section focuses on deadlines. Production refresh tokens expire after 30 days of inactivity starting November 4, 2026, which can break low-frequency integrations. The OAuth 2.0 device flow is restricted from November 30, 2026, and the username-password, user-agent and hybrid user-agent flows are retired on February 20, 2027. Salesforce to Salesforce retires in Spring ’27, and cross-org adapter authentication must move to Named Credentials. Connected Apps lose support by Summer ’27, so teams should move to External Client Apps, which are closed by default. The guide advises inventorying integrations, defining each trust boundary, and choosing replacements that will not face further restriction.

The capacity section covers higher limits and their risks. Synchronous Apex heap rises from 6 MB to 10 MB and asynchronous heap from 12 MB to 25 MB, so workarounds may be simplified. Elastic Async Apex Jobs (Beta) now covers batch jobs as well as future and Queueable jobs, with extra capacity capped at the lower of the licensed limit or 2 million jobs, and should be tested in non-production first. Flow improvements may make Apex built around older constraints unnecessary. Retained manual shares on ownership changes can replace recreation logic, but processes that depend on ownership changes removing access need review.

For Agentforce, Multi-Agent Orchestration is generally available and should be treated as a design-time topology decision. The API Catalog should be governed as the control point for the MCP servers and APIs agents can call, and Data 360 hierarchies should be planned as a data-architecture task. Governance tools include Security Health Review, Scale Center, MCP Server Monitoring (Beta) and Security Mesh. Each has edition, license or support-plan limits, and the guide names fallbacks such as Health Check, debug logs and existing observability tools. The guide closes by recommending an architectural decision record for each significant change.

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

Worth reading?

RecommendedAgentforce and AI

How Salesforce engineered persistent memory for Agentforce agents (opens in a new tab)

You will learn how the Agentforce team designed persistent memory to solve stateless agent limitations, including retrieval strategies, latency tradeoffs, and privacy controls.

Why read this

Readers will understand why memory was moved into the Reasoner and how to enable it using Agentscript.

The Salesforce Engineering team built Agentforce Memory to eliminate the stateless nature of enterprise AI agents. Without persistent memory, users must repeatedly provide context, which increases friction and slows task completion. The team standardized industry terminology around memory types before designing the architecture.

Early prototypes relied on recent conversation history, but the team shifted to semantic retrieval to capture older but relevant information. They evaluated multiple approaches and selected keyword search during pre-orchestration to keep the context window bounded and minimize latency. Moving memory directly into the Reasoner replaced manual action configurations, simplifying administration and improving developer ergonomics.

Privacy and user control were treated as core architectural requirements rather than afterthoughts. Administrators can enable memory globally, while individual users manage preferences through a console or conversational commands. Enabling the feature requires adding a context.memory block to Agentscript, allowing the platform to handle curation and injection automatically.

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

Worth reading?

Releases

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?

Releases

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?