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?

Recommended

Builder Central is a beta hub for building apps and agents in plain language (opens in a new tab)

You will learn what Builder Central does beyond Setup with Agentforce, how its metadata visualizations and preview orgs protect your org, and the steps to enable the beta.

  1. Describe the app or agent in plain language
  2. Answer clarifying questions
  3. Review metadata and test in preview org
  4. Deploy to sandbox via Lifecycle Center
Builder Central takes a solution from plain-language idea to sandbox deployment

Builder Central is a new no-code experience in beta that lets admins build and deploy apps and agents from plain-language prompts. It works as one hub for work that would otherwise be spread across Setup and several builders, and it draws on the org’s existing data model, configuration, security and permissions so that what it creates fits the business and inherits access controls.

The article distinguishes it from Setup with Agentforce, which makes direct, simple administration changes such as creating a field. Builder Central targets larger builds like full data models, flows and agents. It asks clarifying questions before building, deploys through Lifecycle Center, and complements Flow Builder, Lightning App Builder and Agentforce Builder rather than replacing them.

To keep orgs safe, it offers interactive metadata visualizations for reviewing generated components and ephemeral preview orgs, temporary clones of a sandbox, where solutions can be tested before anything is published. To start, admins grant the Access Builder Central user permission, enable the beta feature and activate the Metadata Experts MCP Server in Setup, ideally in a Developer or Developer Pro sandbox.

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

Worth reading?

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?