Today8 stories · 1 brief

The Daily Org

Spring '27Sandboxes 6 Feb 2027

Curated by Abhinav (opens in a new tab)

Vol. I · No. 11The independent daily for Salesforce admins, developers and architects8 stories · 1 brief

Must-readLWC and UI

Salesforce Multi-Framework now supports Angular, microfrontends, and Managed Packages (opens in a new tab)

Readers will learn how to build, embed, and distribute Angular applications directly on the Salesforce Platform using the new Multi-Framework runtime.

Why read this

The article also covers secure cross-app communication, localization, and enterprise authentication requirements.

Multi-Framework runtime capabilities

  • Angular framework support
  • Microfrontend embedding
  • Managed packages
  • Localization and internationalization
  • Multi-factor authentication
  • Multi-Framework Insights
The Winter '27 release introduces key enhancements to the Multi-Framework runtime

Salesforce Multi-Framework is a framework-agnostic runtime that lets developers run modern web apps directly on the Salesforce Platform, inheriting Salesforce authentication, security and governance without a separate hosting stack or manual token handling. After React reached general availability, the Winter ’27 release adds Angular as a second GA framework, with internal, external and basic templates, deployment as a UIBundle metadata type, and the same Data SDK and security model that React apps use. Internal apps run on the Salesforce.app domain, which isolates them from the Lightning runtime and from each other, while platform rules for object-level security, field-level security, sharing and validation continue to apply to data requests and saves.

Microfrontend is now generally available, allowing externally hosted React or Angular apps to be embedded in Lightning Experience, Experience Cloud, the Salesforce mobile app and Mobile Publisher apps without rebuilding them in Lightning Web Components. The lightning-ui-embedding component hosts the app in a sandboxed iframe and provides a two-way channel: hosts pass properties down and embedded apps send custom events back. Managed packages can now distribute non-site, employee-facing Multi-Framework apps together with their supporting metadata such as Permission Sets, Apex and Custom Objects, though site-based apps are not supported. The release also adds locale-aware formatting and localized labels through the Platform SDK and Data SDK, enterprise multi-factor authentication managed by Salesforce, and Multi-Framework Insights in Beta for performance and usage reporting.

The article also describes three ways to build these apps: Agentforce Vibes, now with Angular support and generally available, for code-first development; Builder Central in Beta for natural-language app creation by admins; and Quick Pages in Beta, where business users describe a page in plain language and get a data-driven page that respects the viewer’s security. Salesforce says Vue is the next UI framework planned, along with agentic experiences and Government Cloud support.

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

Worth reading?

Must-readIntegration

Salesforce retires the OAuth username password flow and guides migration to client credentials (opens in a new tab)

Readers will learn how to identify integrations still using the retiring authentication method and follow step-by-step instructions to migrate them to supported flows like client credentials or web server with PKCE.

  1. Create an External Client App
  2. Configure the Run As User
  3. Get the Client ID and Client Secret
  4. Update the Authentication Request
  5. Handle Token Expiration
Migration steps to replace the retiring OAuth username-password flow with the client credentials method

Salesforce will retire the OAuth 2.0 Username-Password Flow on February 20, 2027. The flow has an external application send a Salesforce username, password and security token to the token endpoint. Salesforce first announced the change in Spring ’26 and later moved enforcement from Winter ’27 to the Spring ’27 release. The article calls this a breaking change: integrations that still use the flow will fail when they request new access tokens after enforcement, and the failures may go unnoticed, such as a scheduled job that quietly stops updating records. Orgs created in Summer ’26 and later already block the flow, and the article says that an org with no matching release update may already be blocked.

To find affected integrations, the article recommends several checks. Create a Login History view filtered on the OAuth Username-Password login subtype, keeping in mind that history is kept for about six months, so an empty result does not prove that nothing is affected. Review Connected Apps in App Manager, although the Connected Apps OAuth Usage page does not show these integrations. Search middleware, custom code and repositories for grant_type=password, the Resource Owner Password Credentials term and calls to the token endpoint, checking the grant_type value because other flows use the same endpoint. Managed packages and third-party applications also need review, and the article suggests asking vendors whether they use the flow and what update is required.

The replacement depends on the integration. Client Credentials suits server-to-server work, Web Server Flow with PKCE suits applications that act for individual users, and JWT Bearer suits certificate-based server-to-server setups. For Client Credentials, the article describes creating an External Client App with the api scope, enabling the flow, and choosing a Run As user with only the permissions the integration needs. It also warns that a different user may lack the original user’s record access. The token request changes to grant_type=client_credentials without a username or password. Because this flow issues no refresh tokens, the integration should request a new token when the current one expires, not for every call, and should include retry handling.

The PKCE flow sends users to Salesforce to sign in and authorize the app, then exchanges an authorization code and a code verifier for a token, and it can use refresh tokens. JWT Bearer uses a signed assertion checked against a certificate, which means certificates must be managed. The article also notes that legacy Connected Apps lose full support in Summer ’27, and that migrating one to an External Client App does not fix the username-password dependency, because External Client Apps do not support that flow.

To test, the article advises disabling the Allow OAuth Username-Password Flows setting in a sandbox under OAuth and OpenID Connect Settings, then running each integration. Successful connection tests can be misleading because cached sessions may keep working for a while, so each integration should obtain a fresh token through a supported flow. Failures may show an invalid_grant error and an OAuth Username-Password Flow Disabled status in Login History. The article’s main advice is to start the inventory and migration well before the deadline.

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

Worth reading?

RecommendedIntegration

How to stream Salesforce Platform Events to AWS using Event Relay and EventBridge (opens in a new tab)

You will learn how to configure Salesforce Event Relay to publish custom Platform Events to Amazon EventBridge without middleware.

Why read this

The guide covers channel setup, payload structure, error recovery options, and capacity limits so you can design a reliable integration.

Organizations often rely on expensive middleware to synchronize Salesforce data with AWS applications. This article demonstrates a direct integration path using Salesforce Event Relay and the Amazon EventBridge partner connection, removing the need for third-party platforms. The example tracks Account creation and pushes the details to a DynamoDB table.

The configuration requires a Named Credential pointing to the target AWS account, a Channel grouping the specific Platform Event type, and an Event Relay linking the two components. Once activated, Salesforce publishes record changes to its internal event bus. The relay reads these messages and forwards them to a dedicated AWS partner event bus, maintaining delivery state to resume after transient failures.

The relayed payload places event fields under a detail node, allowing AWS routing rules to send messages to an SQS queue for buffering before a Lambda function processes them into DynamoDB. The author highlights critical operational parameters, including the seventy-two hour retention window, LATEST versus EARLIEST error recovery modes, daily delivery quotas per edition, and the necessity of designing idempotent consumers to handle duplicate messages during failover.

Read the original at dev.to (opens in a new tab)

Worth reading?

RecommendedAgentforce and AI

Using the JSON Path function in AgentScript to extract and filter data (opens in a new tab)

Readers will learn the syntax and practical examples for using the JSON Path function in AgentScript to select, range, and filter data from action responses without writing Apex or Flow.

The article introduces the JSON Path function available in AgentScript, explaining how it extracts data from objects and lists using standard expressions. The function takes three arguments: the source variable, the query path, and an optional default value to return when no match is found. All queries return results as a list.

Several practical examples demonstrate how to navigate nested data structures. The author shows how to retrieve a specific field from a single record, use asterisks to pull the same field from every item in a collection, and apply slice notation to grab a subset of records. Each example includes the exact expression and the resulting output.

Filtering logic allows users to narrow down collections based on conditions before extracting values. The piece illustrates how to combine equality checks and logical operators to isolate records matching multiple criteria. The author warns that while filtering works in sandbox environments, official documentation currently omits these expressions, advising caution before deploying them to production.

Read the original at dev.to (opens in a new tab)

Worth reading?

Releases

A practical framework for managing sandbox previews and testing quarterly Salesforce releases (opens in a new tab)

Readers will learn how to structure their quarterly release cycle using targeted sandbox strategies, filtered release notes, and systematic testing to prevent production issues.

Salesforce ships three releases a year, and the article argues that release readiness should become a routine habit rather than a scramble. It explains the feature lifecycle: Pilot features go to a small opted-in group, Beta features are broadly available for testing with limited support, and Generally Available features are formally part of the release. The author stresses that admins act as product managers for their org, deciding whether to adopt, wait on, or flag each feature. The recommended routine has four steps: plan and learn, get hands-on, test, and communicate.

The planning step covers tracking key release dates, completing the Release Trailhead module, and getting into a pre-release org early. During the roughly four-week sandbox preview window, the author advises keeping a mix of preview and non-preview sandboxes, with non-preview sandboxes forming the deployment path to Production. Deploying from a preview sandbox straight into non-preview Production is the path to avoid, because new metadata such as permissions may not exist there yet and deployments fail. Release Notes are too long to read in full, so the author suggests filtering them with AI tools while keeping a human check on the results, and reviewing Release Updates in Setup well before their enforcement dates.

The hands-on step means exploring features in a pre-release org or preview sandbox, involving power users early, and identifying configuration prerequisites such as page layouts and field-level security. The testing step calls for regression testing in preview sandboxes, ideally with automated tools, verifying suspected bugs in non-preview sandboxes, and opening Salesforce Support cases when problems are confirmed. The author also recommends evaluating new features for business value and compatibility with existing customizations. The final step is communication: sharing knowledge with admins and developers through sessions, preparing training and in-app guidance for users, and meeting people where they already work. The article closes by advising readers to improve one weak step each release.

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

Worth reading?

Flow and admin

Send Custom Notifications in Salesforce using Flow Builder without writing Apex (opens in a new tab)

You will learn how to configure Notification Builder and build a Flow that pushes targeted alerts to desktop and mobile users.

Why read this

The guide covers recipient targeting, deep linking, and best practices to avoid notification spam.

The article explains how to implement Custom Notifications in Salesforce using Flow Builder instead of Apex. It begins by outlining the prerequisite setup in Notification Builder, where administrators define a notification type and select delivery channels such as desktop or mobile.

It then walks through creating a Record-Triggered Flow with entry criteria to control when alerts fire. The guide details how to use the Send Custom Notification action element, wire up the notification type ID, construct dynamic titles and bodies with formula resources, and populate recipient collections using Get Records. It also explains how to set a target ID to enable deep linking directly to the relevant record.

A practical scenario demonstrates using a scheduled Flow to alert managers about stalled high-value opportunities. The author concludes with implementation tips, emphasizing concise titles, aggressive filtering to prevent spam, verifying sharing settings for non-admin testers, and reserving mobile push notifications for urgent escalations.

Read the original at dev.to (opens in a new tab)

Worth reading?

Architecture

Architecting Salesforce Marketing Cloud requires a data foundation before campaign configuration (opens in a new tab)

Readers will learn how to structure data, identity, and consent architectures before configuring journeys in Marketing Cloud.

Why read this

The piece outlines practical questions to answer during implementation planning to prevent scaling failures.

The article argues that Salesforce Marketing Cloud implementations often fail when treated as simple campaign setups rather than comprehensive data projects. It emphasizes that reliable personalization depends on a foundational layer that handles data trust, identity mapping, consent tracking, and system integration before any journeys are built.

It outlines key architectural decisions that must be made prior to configuration, such as identifying authoritative data sources, selecting shared attributes for decisioning, and determining refresh frequencies. The author warns against indiscriminately loading every available field into Data Extensions, recommending instead a focused dataset that supports cross-journey personalization.

Identity resolution and consent management are highlighted as critical components that require business-led decisions rather than pure platform configuration. While tools like Data 360 can consolidate records, organizations must define trusted identifiers, handle duplicates, and map household relationships. Consent must be modeled across channels, geographies, and purposes to ensure accurate suppression and compliance.

Finally, the piece advises designing integrations around business journeys rather than creating point-to-point connections between systems. It recommends evaluating implementation partners based on their ability to establish governance rules, reusable journey patterns, and clear data ownership, ensuring the platform remains sustainable as campaign volume grows.

Read the original at dev.to (opens in a new tab)

Worth reading?

Integration

Connecting Slack to Salesforce for record context and automated alerts (opens in a new tab)

Readers will learn how to use Guided Slack Setup to link a workspace, place the Slack component on record pages, and route Flow notifications to channels.

The article outlines the steps for linking a Slack workspace to a Salesforce org using the native Guided Slack Setup flow. Administrators verify the connection status, authenticate with Slack, and mark each configuration step as complete to maintain a clear rollout trail.

Once the connection is active, the Slack component can be added to Lightning Record Pages through App Builder. This places conversation history directly on layouts for objects like Accounts, allowing team members to view messages and reply without leaving the CRM while preserving record context.

The guide also demonstrates how to send automated alerts to Slack channels by configuring Flow Builder processes that trigger on stage changes or escalations. Users gain the ability to search for records and update fields from within Slack, with modifications syncing back to Salesforce in real time.

Rollout recommendations stress validating permissions with standard profiles, launching with a single object, enforcing consistent channel naming, and tracking adoption rates to optimize component placement and workflow design.

Read the original at dev.to (opens in a new tab)

Worth reading?

In brief