Today6 stories

The Daily Org

Spring '27Sandboxes 6 Feb 2027

Curated by Abhinav (opens in a new tab)

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

Must-readApex and platform

Custom Metadata Types as one deployable home for values across Salesforce and Agentforce (opens in a new tab)

You will see how one Custom Metadata Type can feed formulas, Validation Rules, Flow, Apex and Agentforce actions, and where those references stop working.

Typed into each tool

  • Thresholds in formulas
  • Defaults in Flows
  • Feature switches in Apex classes
  • Each change means finding every use

Custom Metadata Types

  • One deployable home for values
  • Travels through source control
  • One record per region plus Default
  • Read via $CustomMetadata reference
One deployable home replaces values typed into each formula, Flow or Apex class

The article argues that developers often hard-code business values such as thresholds, defaults, feature switches and mappings into formulas, Flows and Apex without noticing, which makes later changes hard to trace. Custom Metadata Types offer a central, deployable home for these values. Unlike Custom Settings or Custom Objects, which hold data, Custom Metadata holds configuration that ships with application code through source control and CI/CD. The author illustrates this with a Deal_Policy__mdt type holding a shared maximum discount and regional records for large-deal amount, default discount and approval threshold, selected by region name.

The piece then maps where references work. Formula Fields, Validation Rules and field defaults can use a three-part reference (type, record name, field), but the formula must name a fixed record, so it cannot pick a region from opportunity data. Long text area fields cannot be referenced, and the formula editor does not list Custom Metadata fields for defaults, though typing the reference still works. Flow can query the type with Get Records, match a region, and fall back to the Default record, and it can also use the literal reference. Apex uses getInstance with a similar fallback. Custom Permissions are kept separate, since they govern what a user may do while Custom Metadata governs the values.

Agentforce cannot read $CustomMetadata references directly, so the workaround is an invocable Apex action that loads the policy and returns the values, which the Agent Script maps into variables before answering. Lightning App Builder component visibility does not accept Custom Metadata references. On record pages a Formula Field can bridge the value, though that adds a field, and App and Home pages must read the data in Apex, through @wire, or via Dynamic Interactions.

To assess impact, the article recommends Setup’s Where is this used? option or a Tooling API query of MetadataComponentDependency, which lists the Apex classes and Validation Rules that depend on a field. It also notes that an attempt to build an LWC editor that showed these dependencies from Apex was complicated by the authentication setup REST calls require. Finally, it outlines platform limits: 200 types per org (350 with certified managed packages), 100 fields per type, and a 10 million character budget where each text area reserves 255 characters regardless of use. Process Builder allows 15 Custom Metadata formula references per process. The author concludes that teams should treat business values as configuration, centralize them, and keep track of where each reference works and where it does not.

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

Worth reading?

Must-readFlow and admin

Winter '27 lets admins trigger Screen Flows from List Views and Related Lists (opens in a new tab)

A step-by-step setup for the Winter '27 feature that passes the records a user selects in a List View or Related List into a Screen Flow.

  1. Build Screen Flow with ids variable
  2. Create Flow action on the object
  3. Add to List View Button Layout
  4. Add to Dynamic Related List – Single
Setup for running a Screen Flow on selected records

Starting in Winter ’27, users can select several records in a List View or a Related List and hand them to a Screen Flow that opens in a modal. The article treats it as an overlooked part of a large release because it lets admins build mass actions without code.

The setup has one detail that is easy to miss. The flow needs a text collection variable named ids, in lowercase, marked as available for input. The selected record Ids arrive in that variable. The example flow gets the matching Contacts, shows them in an editable Data Table on a screen, and writes the edits back with an Update Records element, with fault paths on the data elements.

To expose it, create an action of type Flow on the object and add it to the List View Button Layout under the Lightning Experience List View actions. For Related Lists, create the same kind of action, then add it to a Dynamic Related List – Single component on the parent’s Lightning Record Page.

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

Worth reading?

RecommendedAgentforce and AI

Salesforce engineers use Agent Graph to keep AI-drafted Prompt Templates reliable (opens in a new tab)

This explains how Salesforce keeps LLM-assisted prompt creation deterministic: graph-controlled routing, server-side record identity mapping, and sentinel-tagged structured output.

Why read this

It is useful if you are designing any AI feature where model output must remain safe and schema-valid.

Salesforce engineers describe building Assistive Authoring for Prompt Builder, which turns a plain-English requirement into a working Prompt Template in under a minute instead of the roughly 25 minutes an experienced admin needs today. The core risk they targeted was not obviously bad output but plausible-looking templates that break at runtime because the model invented a field, corrupted a record ID, or returned malformed metadata.

The solution uses Agent Graph to split the work into a router node and three specialized sub-agents for generating, refining, and clarifying requests. State variables carry client-supplied and runtime context, bound inputs pass only what each tool needs, and four backend tools run in a fixed sequence with a beforeReasoning hook that fetches grounding before the model loop starts, cutting latency by removing a model decision from the critical path.

Deterministic boundaries protect the three failure points. The model can signal intent through a state variable, but the graph evaluates guards before changing nodes. The model never touches record IDs; it writes stable developer names and a server-side transpose layer maps them back to real records and IDs. Template metadata is wrapped in sentinel tags, the client extracts and parses only that payload, and parse failures return errors rather than guesses.

Grounding is handled by a discovery service that normalizes SObject fields, flows, Apex-backed providers, and search retrievers into one consistent shape, runs in the current user’s context with field-level readability filtering, and reduces the result to an allowlist the model must select from. Safety is enforced by making output a draft only: the agent has no tool to save, publish, or execute, content becomes typed editor blocks with escaped interpolation, and the admin accepts or rejects a diff before anything is saved.

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

Worth reading?

Agentforce and AI

Agent Designer automates multi-agent AI team design, verification, testing, and repair (opens in a new tab)

You will see how Salesforce governs autonomous agent teams with topology-aware budgets, structured verification contracts, and hard caps on self-repair.

Why read this

The governance patterns around write boundaries and failure classification are transferable to anyone building agentic systems.

The article profiles Agent Designer, an internal Marketing Cloud system that automates the design, verification, testing, and repair of multi-agent AI teams, reducing the cycle from two to four hours to roughly 15 to 30 minutes. Engineers previously hand-authored YAML files, prompts, profiles, tools, models, budgets, and turn limits, then tested and iterated manually. The new system uses an orchestrator that dispatches and verifies work but is prohibited from writing any agent file, supported by seven specialists that each carry their own model, budget, and turn limit, and it has helped about 200 engineers adopt a manager-of-agents model.

Multi-agent governance proved harder than single-agent configuration because independently valid specialist outputs can combine into an unbuildable design. Architecture, failure-mode, and compliance analysts work in parallel without seeing each other’s findings, so the orchestrator must detect contradictions and apply bounded remediation rather than restarting the analysis. Since the agent specification lacked a native write-scope field, write boundaries are enforced in prompts, and teams created through Claude Unleashed must define exactly one coordinator and pass a compatibility validation.

Budget enforcement is topology-specific: a flat check for a single agent, items times cost times steps for a swarm, and whole-roster ceilings for a team, all fitting inside the orchestrator’s 500-turn budget that is divided across analysis, approval, generation, testing, and retries. Verifiers return structured PASS, WARN, or FAIL blocks with rules such as warning rather than failing when uncertain, and the orchestrator runs a meta-check across their outputs. A test doctor classifies failures into categories including soft failures that require point-by-point comparison against expected behavior, and self-healing is capped at two fix attempts and a three-dollar ceiling before the system stops and escalates to a human.

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

Worth reading?

Agentforce and AI

Agentforce Coworker setup, security and routing within AIforce (opens in a new tab)

It explains how Agentforce Coworker fits into the AIforce stack, how its routing and security model work, and gives a concrete setup path via Data 360 and Salesforce Go.

Agentforce Coworker is presented as one of three main pillars of AIforce, Salesforce’s interface layer announced at Dreamforce ’26. Its purpose is to bring Salesforce data and agents to where users already work, such as Lightning Experience, Slack, Microsoft Teams or AI tools, instead of making them switch between applications. It targets two problems: tab-switching between many tools, and users struggling to know which agent to use for a task as agentic workforces grow. It acts as a router agent, the front door to an org’s agents, sending queries to the right one. Its foundations are Agentforce (the digital workforce layer it orchestrates), Customer 360 (CRM as the unification point for customer data) and Data 360 (the grounding layer that indexes and governs data for AI).

The piece describes three interaction modes. Find lets users ask questions in plain language and get contextualized answers drawn from CRM data, Slack, files, knowledge bases and other connected sources. Catch Up proactively surfaces changes in the user’s scoped workspace, such as what they missed while in meetings. Plan and Act takes outcome-level instructions and routes the work to the appropriate agent. Security relies on the existing Salesforce model: profiles, Permission Sets and Sharing Rules still apply, so Coworker only sees what the user is allowed to see, following least privilege.

The author’s hands-on setup path begins with confirming Data 360 is enabled, checked under Data Cloud Setup Home, and assigning the Agentforce Coworker Admin Permission Set to administrators. Coworker is then switched on through Salesforce Go by searching for it in Setup. Administrators choose data sources under Manage Data, with CRM data enabled by default. Finally, users need the Agentforce Coworker User Permission Set, which can be assigned via Manage Access to Agentforce Coworker in Manage Users. In use, the Ask button beside global search opens the Ask: Home tab, and the author recommends starting a fresh session for unrelated prompts to avoid carrying over context.

The article closes with caveats. Data 360 must be enabled before Coworker works, though not every data set must be shared with it. Coworker is available in Enterprise, Unlimited and Agentforce 1 Editions. Billing is either consumption-based through Flex Credits or seat-based with usage caps, so costs can rise quickly and the author suggests monitoring value with tools such as Agentforce Grid and Agentforce Observability. The author also advises planning and cleaning data and permissions before rollout.

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

Worth reading?

Architecture

Cloud Atlas replaces per-instance rate limits with fleet-wide protection (opens in a new tab)

An inside account of why per-instance rate limits failed for the identity store behind Salesforce authentication, and what replaced them.

Cloud Atlas is the globally distributed identity data store behind a large share of Salesforce logins and token validations, run to five nines of availability. In this interview, the team’s engineering lead explains why overload at that layer is dangerous: slow responses cause upstream services to retry, the retries add traffic to a system already under pressure, and a local bottleneck spreads. Agent-driven and automated workloads have made traffic burstier and harder to predict than human logins.

The old protection was per-instance rate limiting. That held up while infrastructure was static, but with autoscaling each server’s limits went stale whenever instances were added or removed, and each server knew only its own load rather than a customer’s total usage across the fleet. Busy servers rejected requests while capacity sat idle elsewhere, and one tenant’s spike could still starve others.

The redesign protects the service as a whole instead of individual servers. It combines global quota management that needs no central coordinator with load shedding that acts before retries begin to amplify the overload, so a single customer’s surge is isolated rather than shared.

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

Worth reading?