The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Recommended

Builder Central lets admins build and edit in a virtual layer before touching the sandbox (opens in a new tab)

You will learn how Builder Central keeps proposed metadata changes out of your sandbox until you approve them, how it edits existing flows and apps, and what its new project-plan review step does.

Why read this

The piece is a podcast transcript, so the specifics are mostly the speakers' claims and a demo.

  1. Describe the idea in Builder Central
  2. Review the project plan before building
  3. Explore changes in the virtual environment
  4. Publish to the sandbox on your approval
How a Builder Central change reaches the sandbox, as described in the episode

Builder Central, now in beta, is a Salesforce tool that lets admins go from a description of an idea to a working solution on the platform without writing code. The podcast hosts describe it as the result of about two and a half years of internal work, built on the team’s headless and MCP efforts, and aimed at low-code builders. Early customers reported that tasks which took seven to ten days for several people now take one person two to three hours.

The central design point is that Builder Central works in a virtual environment rather than changing sandbox metadata while you build. Changes stay out of the org until you explicitly publish the project to the sandbox with a button or by asking the agent to do it. Visualizers show flows and other output as they would look in the org before anything is deployed, and the speakers say the team keeps adding them.

The tool also covers the maintenance work that makes up most of an admin’s job. Because it can read all the metadata in an org, it can refactor or test existing flows, and the hosts say it generated flow tests that a product manager judged to be good. A feature due around TDX will let users pull an existing app into a project and restyle it with a brand kit. A new step, rolling out that week, has the agent build a project plan for the user to review and approve before it starts building, and inline editing lets users select a single component to change.

The episode is promotional in tone and mostly anecdotal, so treat the productivity figures and comparisons with Claude Code as the speakers’ own account. The practical takeaway is the publish-on-approval workflow and the plan review step, which are the parts most relevant to governance and sandbox risk.

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

Worth reading?

Must-read

Testing Salesforce Flows locally with renmy runtime before activation (opens in a new tab)

You will learn how to run Record-Triggered Flows and Apex triggers on a local machine, catch order-of-execution overlaps before activation, and what the runtime does not cover.

  1. Retrieve flow into project folder
  2. Write test creating and closing record
  3. Run renmy test locally
  4. Fix overlap, rerun in seconds
  5. Activate and review in sandbox
A local test run replaces repeated sandbox rounds for checking flow and trigger behaviour

renmy runtime, formerly called Nimbus until its October 2026 rename, is a local Salesforce Apex runtime. It executes Apex, SOQL, DML and Salesforce Flows (Autolaunched, Record-Triggered and Screen Flows) on a developer’s own computer against an embedded database, with no org, sandbox or Scratch Org involved. The article argues that testing flows in a shared sandbox is slow and risky: other people’s automation fires alongside yours, test data disappears after refreshes, and overlaps between a flow and an Apex trigger on the same object often surface only after activation. Running locally, a Record-Triggered Flow fires together with the object’s triggers in the platform’s order of execution, so overlaps show up in milliseconds.

The article walks through an example: a Record-Triggered Flow that creates a follow-up Task when an Opportunity is set to Closed Won, alongside an older Apex trigger that also creates a Task. A developer retrieves the flow file into the project folder with the Salesforce CLI. They then write a short Apex test that creates an Account and an Opportunity, moves the stage to Closed Won, and asserts that exactly one Task exists with the expected subject. The admin can read that test as an acceptance criterion. Running renmy test with the test name, or with “” for every test, reports the result. If the trigger also creates a Task, the assertion fails with two Tasks, revealing the overlap. The fix is either to remove the trigger’s logic or to add an entry condition to the flow, and the rerun takes about a second. Once the flow is ready, renmy deploy runs the local checks before anything reaches the org.

The same runtime is available through a browser-based Dev UI started with renmy dev, which offers a test runner, schema browser and coverage explorer. A VS Code extension adds run buttons above each test, and a JetBrains plugin does the same in IntelliJ IDEA, including its Community edition, and can display a flow as a graph. The article is clear about the limits. The runtime executes a Screen Flow’s logic but does not render its screens, so layout, labels and conditional visibility must be checked in a sandbox with a user. It reproduces platform rules closely but is not Salesforce itself, and permissions, page layouts and user acceptance still require an org. The Free tier includes unlimited local test runs on one machine, with no account or card required.

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

Worth reading?

Must-read

Salesforce introduces beta Test Mode for Flow debugging and regression testing (opens in a new tab)

You will learn how to enable and use the new Test Mode beta to save, reuse, and automate Flow validation without leaving the builder.

Why read this

You will also understand upcoming capabilities like element mocking, test coverage tracking, and Agentforce powered troubleshooting.

Traditional Approach

  • Debug button only for troubleshooting
  • Testing and debugging require separate actions
  • Manual checks lack reusable configurations
  • Cluttered design canvas during validation

Test Mode Workspace

  • Dedicated view replaces Debug button
  • Merges debugging and automated testing
  • Saves runs as reusable manual test scenarios
  • Converts manual tests to regression tests with assertions
How Test Mode consolidates Flow debugging and automated testing

Salesforce has released a beta version of Test Mode, a dedicated workspace that replaces the traditional Debug button in Flow Builder. This update merges debugging and automated testing into a single interface, requiring administrators to enable the feature through Process Automation Settings before it becomes available for Record-triggered and autolaunched flows.

The new workspace allows builders to save execution runs as reusable manual test scenarios. These saved configurations preserve triggering records, input variables, and mocked outputs. Administrators can now supply static record identifiers for poorly searchable objects and populate primitive collections directly in the test panel. Once validated, these manual scenarios can be transformed into permanent regression tests by attaching expected results.

Test Mode also introduces element mocking, which simulates outputs for subflows and external actions to keep testing isolated from live endpoints. The roadmap includes Winter ’27 enhancements such as visual test coverage tracking on the canvas and Agentforce powered capabilities. These future features will synthesize transaction context to diagnose cross automation failures and automatically generate comprehensive test scenarios with isolated data silos.

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

Worth reading?