Today4 stories · 1 brief

The Daily Org

Spring '27Sandboxes 6 Feb 2027

Curated by Abhinav (opens in a new tab)

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

Must-readReleases

B2C Commerce October 2026 release adds events GA and self-service unpairing (opens in a new tab)

You will learn what the October 2026 B2C Commerce release changes for integrations, environment setup and licensing, including the Event Framework going generally available and the removal of the Data 360 license requirement for the trusted connection.

Why read this

You will also see which agentic and developer tooling features arrived with it.

Before October 2026

  • Data 360 license needed
  • Admin support ticket to reset pairing
  • Sandbox type limits

October 2026

  • No Data 360 license needed
  • Self-service unpairing
  • Any Salesforce sandbox type
Trusted connection to a Salesforce org no longer requires a Data 360 license

The October 2026 release for B2C Commerce focuses on speed, automation and unified commerce. It adds Universal Commerce Protocol integration, which lets merchants turn on UCP-powered checkout on Google so shoppers can buy directly from surfaces such as the Gemini app and Google Search while the merchant stays the merchant of record. Agentic features built into Business Manager include conversational catalog search, where the Merchandising Agent builds filter logic from plain English, and AI-suggested category assignments with a dashboard insight for uncategorized products.

For integration work, the most relevant changes are the Event Framework going generally available, with process-level and granular replication events, shopper registered and order placed events routed to HTTP webhook connectors, and support for custom events declared in a cartridge. The trusted connection to a Salesforce org no longer needs a Data 360 license, admins get self-service unpairing after a sandbox refresh, and developers can pair non-production instances with any Salesforce sandbox type. Profile updates now sync to connected Person Accounts in near real time, and partial POS catalog syncs let stores receive only modified pricing and product data.

On the tooling side, the Agentic Developer Toolkit gains more built-in knowledge, new operations runbooks that always ask for approval before making changes, and SCAPI Code Mode, which lets an AI assistant look up Salesforce Commerce API operations and run small scripts against a live instance. Direct SCAPI security controls for rate limits, WAF rules and cache purges are also available in Business Manager or by API.

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

Worth reading?

RecommendedAgentforce and AI

Agent Fabric adds evals, kill switch and hard spending limits for agents (opens in a new tab)

You will learn what Agent Evals, API Evals and the cost controls in Agent Fabric do, and how automated quarantine and budget caps are meant to work once an agent is in production.

Why read this

The article also notes that these checks are only as good as the tests and thresholds behind them.

  1. Scheduled tests run on the agent
  2. Quality issue flagged by Agent Evals
  3. Approval requested to quarantine agent
  4. Instructions revised and evaluation rerun
How Agent Evals responds when an agent's quality drops after a model change

Salesforce is introducing Agent Evals, API Evals and advanced cost controls for Agent Fabric, its control plane for AI agents. The company says that problems in agents, such as changes in models, APIs or costs, can surface silently, and that resolving them today means finding the owner and getting approval to restrict an agent while it keeps producing bad results and spending tokens.

Agent Evals generates tests before deployment and then evaluates agents, LLMs and MCP servers in production. When results fall below the evaluation standards, predefined interventions such as the Agent Kill Switch are triggered, subject to approval where a team’s policy requires it. API Evals creates functional and performance tests from API specifications so that breaking changes are caught before production. The FinOps Dashboard and Model Wallet show AI spending and enforce hard limits that can stop requests before a budget is exceeded, and Cost Optimization Policies are said to cut token usage by up to 75 percent in test scenarios through semantic caching, payload compression and response trimming.

The article gives a retailer example in which a switch to a cheaper model leads scheduled Agent Evals runs to find inaccurate delayed-order answers, after which the agent is quarantined with approval, its instructions are revised, and the evaluation is rerun before it returns to production. The author closes by noting that the Agent Kill Switch is the main takeaway, and that the value of these evaluations depends on the tests and thresholds behind them.

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

Also told by Salesforce News (opens in a new tab)

Worth reading?

Flow and admin

Builder Central turns a requirements prompt into a working Salesforce app (opens in a new tab)

You will learn how Builder Central plans and builds a Custom Object, List View and Permission Set from a plain-language prompt, what it leaves for the Admin to finish, and how it fits beside Lightning App Builder and Flow Builder.

  1. Describe the app in a prompt
  2. Review the project plan
  3. Build in a separate workspace
  4. Publish to the org
  5. Assign the Permission Set
The order in which Builder Central moved the Bulk Delivery Management app from prompt to live use

The author tested Builder Central, a beta conversational workspace for planning, building, previewing and deploying Salesforce apps and agents from plain language. He described a spreadsheet replacement app in one prompt, naming a Custom Object and its fields, and Builder Central first produced a project plan for review before building anything in its own separate workspace.

After the initial build it suggested extra customization, such as a List View, which he accepted. He published the app, asked Builder Central to assign the Permission Set to his user, and then opened the app from the App Launcher. The build took about 12 minutes in real time, though he sped up parts of the video.

The result was not complete: the record page did not show all fields, so he adjusted it in Lightning App Builder. He argues the change matters less for saving time than for shortening the loop between requirements meetings and a working prototype, while Admins still own permissions, automation, user experience and testing. He recommends trying it in a sandbox, recreating an existing app conversationally, and checking the beta limitations.

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

Worth reading?

Releases

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?

In brief