Today4 stories · 4 briefs

The Daily Org

Spring '27Sandboxes 6 Feb 2027

Curated by Abhinav (opens in a new tab)

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

Must-readFlow and admin

Flow Test Mode adds saved Test Scenarios, assertions and mock outputs to Flow Builder (opens in a new tab)

You will learn how to create and save Flow test scenarios, add assertions and mock external action outputs, and why these tests are not yet enforced at deployment.

Why read this

The piece also notes that FlowTest is a separate metadata type to include when deploying.

  1. Save Test Scenario with inputs
  2. Enable Automated Test Scenario
  3. Add assertions and mock outputs
  4. Run All for coverage and results
How a saved Test Scenario runs automatically with assertions

Salesforce’s Winter ’27 release introduced Flow Test Mode, a dedicated testing canvas for Autolaunched and Record-Triggered Flows that is currently in beta. It is enabled through the Process Automation Settings page in Setup, and the author recommends trying it in a sandbox first. Within the new canvas, builders can debug by record Id or name, test primitive collection variables by separating values with semicolons, and save reusable Test Scenarios with labels, descriptions and run options such as rollback mode. Scenarios can be run manually or set to automatic, with assertions checking expected results, such as whether an element was visited or a field has a given value, and with the choice of which flow versions to test. Mock outputs let builders supply fabricated responses for external action elements, so tests can run without calling the endpoint and can force success or fault paths.

The author highlights practical uses: rerunning a scenario that reproduces a bug until it is fixed, using saved assertions for regression testing after org changes while watching coverage and results, and testing integrations without configuring live connections. He also explains deployment: FlowTest is its own metadata type, separate from the flow, so tests must be packaged and deployed individually. Currently a flow can be deployed without its tests, making them a nice-to-have rather than an enforced requirement as Apex tests are, and the author hopes enforcement will come once the feature reaches general availability.

The piece concludes that Flow Test Mode still falls well short of Apex testing, which requires at least 75% coverage before production deployment and cannot be bypassed, while flows can currently be built directly in production. Mock outputs are a point-and-click analogue of Apex’s HttpCalloutMock approach, and the Test Discovery API can run Apex and flow tests together. Overall, the author sees the feature as a significant and promising step for Flow, though it is still in beta.

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

Worth reading?

RecommendedFlow and admin

Choosing between Record Types, Profiles and Permission Sets (opens in a new tab)

You will learn what each of Record Types, Profiles and Permission Sets is for, and how to decide which one fits a given requirement.

Why read this

The article also explains why Record Types are not a security control.

Record Type

  • Different business processes
  • Controls picklist values per process
  • Not a security control

Permission Set

  • Grants additional access
  • Assigned to selected users
  • Field and object permissions
Each tool solves a different problem, so match the requirement to the right one

This Salesforce Ben article helps admins decide between Record Types, Profiles and Permission Sets when a new requirement arrives. It explains that Record Types support different business processes for the same object, controlling available picklist values through Sales Processes and working with Page Layouts. It stresses that Record Types are not a security mechanism, since assigning one does not govern which records or fields a user can see or edit, and that restricting Record Types does not block access to existing records using other types.

Profiles, which every user has exactly one of, are described as the baseline for a user’s experience, covering login hours, IP ranges, password and session settings, default apps, default Record Types and Page Layouts. Permission Sets add access on top of that baseline, and a user can hold several of them; Permission Set Groups bundle commonly paired sets together. The article notes Permission Sets generally grant rather than remove access, and that a muting Permission Set inside a group only suppresses permissions from other sets in that same group, not those from the Profile or outside the group.

A decision table maps requirements to starting tools, and the article warns that one requirement may need several tools working together. It walks through worked examples: sales-process picklists suit Record Types, a handful of users needing a feature suits a Permission Set, and hiding fields from a Page Layout does not secure them, so field-level security is needed. It closes with five anti-patterns to avoid, including creating a Profile per department, using Record Types for security, duplicating Profiles in Permission Sets, ignoring Record Types in layout design, and letting Permission Sets sprawl, along with a set of questions to ask before configuring. The article also notes that Salesforce’s retirement of Profile-based permissions was cancelled in June 2026, while it still recommends a permission-set-led approach.

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

Worth reading?

Agentforce and AI

Koa Decisions, a small model for fast routing Decisions in Agentforce (opens in a new tab)

You will learn what Koa Decisions is, how it differs from a general-purpose LLM for categorical decisions, and the latency figures Salesforce reports.

Why read this

You will also see the planned extension to flows, Apex and Prompt Templates.

General-purpose LLM

  • Generates text token by token
  • Roughly 1.4 seconds for routing
  • Built for writing and reasoning

Koa Decisions

  • Reads the whole request at once
  • Roughly 26 milliseconds for routing
  • Returns a choice, yes/no or score
A decision model returns a short answer far faster than a general-purpose LLM

Salesforce is releasing a new version of Koa Decisions, an AI decision model built on its HyperClassifier model and trained on Google’s open-weight Gemma. It takes a request and a list of categories you define, and returns a choice, a yes or no, or a score within milliseconds. The latest version adds multimodal support for images and audio.

The article argues that a general-purpose LLM is slower and more costly for quick, targeted decisions such as routing a request to a team. A decision model reads the whole request at once and can return an answer in as little as one token, while an LLM generates text token by token. Salesforce reports that, when routing requests in Agentforce, the decision model took roughly 26 milliseconds against roughly 1.4 seconds for a general-purpose LLM.

Salesforce plans to extend the model beyond routing into flows, Apex and Prompt Templates, with an API for developers. The company frames it as a way to keep larger models for reasoning and generation while smaller models handle routine decisions.

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

Worth reading?

DevOps

Checking a Contact export for orphans, duplicate External IDs and picklist mismatches after a load (opens in a new tab)

You will learn how to count orphaned Contacts, unresolved AccountIds, duplicate External IDs and picklist values outside the allowed API names, using spreadsheet formulas, a standard-library Python script and SOQL.

Why read this

The article also explains what these checks cannot catch.

  1. Export Contacts and Accounts
  2. Flag blank and unresolved AccountIds
  3. Find duplicate External IDs
  4. Compare picklist to allowed API names
Four checks run on the exported files after a load

A successful Data Loader insert or upsert can still leave a Contact export with problems the success file does not show. The article covers blank AccountIds, AccountIds that point to no Account in the export, External IDs shared by more than one Contact, and picklist values that are not among the field’s allowed API names.

The walkthrough works through example files and three methods: spreadsheet formulas that flag each problem column, a Python script using only the standard library, and SOQL queries to confirm the counts against the live org. It notes that SOQL returns picklist API names rather than labels, and that values loaded into an unrestricted picklist can be stored without being listed in Setup.

The author stresses that orphans are a review list rather than a delete list, and that a wrong but existing AccountId needs a separate source-to-target comparison. The example data is fabricated and the reader must adapt field headers to their own org.

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

Worth reading?

In brief