Today4 stories · 1 brief

The Daily Org

Spring '27Sandboxes 6 Feb 2027

Curated by Abhinav (opens in a new tab)

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

Must-readLWC and UI

Using Microfrontends and UI Embedding to integrate external web apps into Lightning (opens in a new tab)

You will learn the architecture behind Salesforce Microfrontends, including how the Lightning host and embedded guest application communicate through UI Embedding.

Why read this

The article provides concrete code examples for building both the LWC host and a React-based guest app.

Microfrontend architecture

  • Lightning host
  • UI Embedding
  • Embedded web application
How Salesforce Microfrontends connect external apps to Lightning Experience

The article introduces Salesforce Microfrontends, which use UI Embedding to bring web applications built with React, Angular, Vue, or other standards-based technologies into Lightning pages alongside Lightning Web Components. The architecture has three parts: a Lightning host (a custom LWC that renders the lightning-ui-embedding base component and owns the Salesforce context and data), the embedded guest web application, and UI Embedding as the managed communication layer between them. The guest runs in a sandboxed iframe, which gives the two applications a browser-enforced isolation boundary. The host decides what information to share, and the external origin must be allowed in Salesforce security settings.

The article illustrates this with a ScoreAccount web app that shows an Account’s rating and lets users choose Hot, Warm, or Cold. The host retrieves the record data and passes the state to the guest, which renders it and subscribes to later updates. When the user selects a rating, the guest dispatches a score event that the host handles by updating the Salesforce record, and the host then sends any changed data back down. The article lists the four steps to bring such an app into Lightning: allow the origin, connect the guest to the UI Embedding channel through the Salesforce Platform SDK, create the host LWC, and deploy both sides through their own workflows. It presents the example in React but notes that the approach is not tied to one framework.

The piece argues that Microfrontends suit established web experiences that a team wants to keep on its own framework, infrastructure, and release cycle, such as an existing analytics app or internal search tool, rather than rebuilding them. It positions Microfrontends as complementary to LWC, which remains the native model for Salesforce-specific experiences, and to Salesforce Multi-Framework, where supported frameworks are packaged as UI bundles and hosted on Salesforce. A comparison table shows that externally hosted Microfrontends run on the team’s own infrastructure, while UI bundles are built and deployed through Salesforce workflows. The article gives UI Embedding’s status as GA since September 2026 and UI bundle embedding as in Beta with GA targeted for mid-November 2026, and it points readers to the UI Embedding recipes and Salesforce Developer documentation for implementation details.

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

Worth reading?

RecommendedAgentforce and AI

Agentforce Service offerings explained for configuration and rollout planning (opens in a new tab)

Readers will learn how to configure and deploy Agentforce Service agents, understand the prerequisites for Omni-Channel routing and Knowledge grounding, and see which legacy channels are being retired.

Why read this

The piece also outlines practical rollout strategies to avoid common implementation pitfalls.

The piece is a guide to Agentforce Service, Salesforce’s AI customer service platform, which was renamed from Service Cloud in October 2025. It covers seven offerings: AI agents, case management, omnichannel contact center, an AI knowledge base, field service, analytics and integrations. For each, it explains what the offering does, what it depends on and where teams tend to run into trouble. The AI agents come in two forms. Help Agent is prepackaged and set up from one screen, and it is grounded on Salesforce Knowledge, uploaded files or a website sync. It needs Enterprise or Unlimited Edition with Agentforce enabled. Service Agent is configurable, with topics, instructions and actions defined by the team, and suits work that touches the company’s own systems, such as order lookups or appointment changes. Agentic features such as Agentic Milestones, MCP support and multi-agent setups are also described. Omni-Channel routing depends on Enhanced Omni-Channel, which the article calls the foundation for Agentforce Service and a requirement for Agentforce Voice and Contact Center.

On the contact center and channels, the article notes that Salesforce is retiring Standard Facebook Messenger and Standard SMS channels in mid-2026, so teams still on them should move to Enhanced channels. It also points to the knowledge base as a dependency: AI answers are only as good as the Knowledge articles behind them, so the author recommends knowledge-centered service habits. Case management, field service work orders, analytics (with metrics such as autonomous resolution rate, escalation rate and CSAT on AI-handled cases) and MuleSoft-based integrations with ERP and telephony systems are each summarized with their key requirements. Pricing mixes per-user licenses, Flex Credits and a per-resolution charge for Help Agent, and the article advises confirming current India pricing with Salesforce.

The rollout advice is the practical core. The author suggests auditing data and the knowledge base first, setting up Enhanced Omni-Channel, launching one AI agent on a single high-volume, low-risk queue, measuring results for a month and then expanding, with budget kept for ongoing tuning after go-live. The article is written by Cloud Odyssey, a Salesforce partner, and it promotes its own services, so its vendor-supplied performance figures (such as 72% of routine inquiries offloaded and 70% resolution on Salesforce’s own help portal) are presented as numbers to test rather than guaranteed results.

Read the original at Cloud Odyssey (opens in a new tab)

Worth reading?

Architecture

Architecting Salesforce orgs for user adoption and phased rollouts (opens in a new tab)

You will learn how to embed adoption criteria into your design phase, optimize Lightning Record Pages and Validation Rules for primary personas, and structure phased rollouts to minimize friction.

The article argues that user adoption failures stem from early architectural choices rather than training gaps. It recommends establishing explicit adoption criteria during the design phase, including identifying primary personas for each object, limiting required fields to initial entry points, and ensuring critical actions require three clicks or fewer. The piece highlights the updated Salesforce Well-Architected Framework, which now emphasizes making design trade-offs visible and documenting their rationale.

To align system workflows with natural user behavior, the author suggests using Dynamic Forms with visibility rules to tailor Lightning Record Pages per role, applying stage-based Validation Rules instead of blanket requirements, and routing approvals without halting progress. Designs should be validated by having representative end users complete common tasks cold, treating any hesitation as a signal to adjust the architecture before configuration begins.

Post-launch success relies on built-in feedback loops and phased rollouts. The author advises capturing adoption signals through Field History Tracking, stage duration reports, and the Lightning Usage App, then shipping corresponding dashboards on day one. Rollouts should avoid big bang deployments by keeping phases independent, using Permission Set Groups for granular feature access, and restricting navigation tabs to only show active waves, thereby containing friction and enabling continuous improvement.

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

Worth reading?

Agentforce and AI

Salesforce introduces Deep Insights and Moirai for real-time operational intelligence (opens in a new tab)

Readers will learn about two new Salesforce AI capabilities designed to analyze live business data and predict trends without manual dashboard monitoring.

Why read this

The piece outlines how these tools reason over structured data and forecast demand using built-in business context.

The article frames enterprise data challenges around the historical analogy of radar, noting that businesses currently lack a layer to make massive real-time data streams legible before action windows close. It introduces operational intelligence as the solution, moving beyond static dashboards toward continuous AI reasoning over live information.

Two specific models power this approach. Deep Insights processes structured business data to trace issues to their root causes and recommend subsequent steps. Moirai handles time-series forecasting by predicting demand and detecting anomalies while automatically incorporating known business variables such as seasonal shifts or renewal waves.

Salesforce is already deploying these capabilities internally. Engineering 360 uses Deep Insights to correlate patterns across ninety billion records, while the Contact Center division applies Moirai to optimize staffing and demand planning. The company plans to extend these reasoning layers across sales pipeline management, marketing performance tracking, and supply chain operations.

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

Worth reading?

In brief