The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Recommended

A four-bucket Kit of 100 prompts for Admin work with Agentforce Vibes (opens in a new tab)

You will learn how the Admin Accelerator Kit's four prompt buckets (Understanding, Configuring, Troubleshooting, Documenting) are meant to be used, and which prompts to run first in a sandbox.

Why read this

You will also see how the buckets chain together on a real change, such as converting a text field to a picklist.

  1. Understanding: map what the org already does
  2. Configuring: plan, then build the change
  3. Troubleshooting: diagnose what breaks
  4. Documenting: record the change and the why
The four prompt buckets are meant to be used in sequence on a single change

The post introduces a set of 100 ready-made prompts for everyday admin tasks, presented at a Dreamforce 2026 session on Agentforce Vibes. The prompts are hosted as a markdown file in the Admin Accelerator Kit on GitHub, and readers can simply browser-copy them. They are organized into four buckets of five categories with five prompts each, and placeholders in angle brackets must be replaced with real API names. The authors note the prompts also work with other agents connected to a Salesforce org through MCP.

The author advises starting in a sandbox or Developer Edition org, especially for Configuring prompts, because Understanding and Documenting prompts mostly read metadata while Configuring prompts change it. Understanding prompts help map objects, Flows, permissions and business processes, and impact-analysis prompts help check what breaks before a field change. Configuring prompts range from “How do I” questions that yield click paths to “Create” and “Write” prompts that generate Flow or Validation Rule metadata for review before deployment.

Troubleshooting prompts cover Flow errors and permission problems, with the advice to paste the full fault email along with record IDs and the affected user. The kit also addresses conflicting automations that silently revert field values. Documenting prompts produce data dictionaries, release notes, deployment checklists and, most importantly, a record of why a rule was configured as it was.

The post closes by showing the buckets chained together on a Region picklist change, and invites feedback and contributions to the kit’s repository.

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

Worth reading?

Recommended

Agentforce Specialist exam outline updates and a four-week study plan (opens in a new tab)

Readers will learn the updated Spring 2026 Agentforce Specialist exam structure, key topic weights, and a hands-on preparation plan using Developer Edition orgs and core platform tools.

The Spring 2026 Agentforce Specialist exam has been restructured, removing separate Sales Cloud and Service Cloud sections while adding Agent Script, hybrid reasoning, Testing Center workflows, governance, and multi agent orchestration. The assessment consists of 60 scored multiple choice questions plus five unscored ones, lasts 105 minutes, requires a 72 percent passing score, and costs 200 dollars to register.

A four week preparation strategy emphasizes practical application over rote memorization. Week one focuses on prompt engineering and the Trust Layer using field generation and flex templates grounded in record data. Week two covers Data Cloud fundamentals, guiding readers to build a file based Data Library and connect policy documents to test retrieval behavior. Week three shifts to agent creation, requiring the construction of an agent with Flow backed actions and deterministic decision filters. The final week covers the Testing Center, deployment procedures, analytics, and governance monitoring.

Common study mistakes include relying on outdated outlines, underweighting the AI Agents section, treating Data Cloud as optional, and ignoring annual maintenance requirements that expire the certification. The article concludes that demonstrating configured solutions and tested agents during technical interviews carries more weight than the certification badge alone.

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

Worth reading?

Managing Restricted Picklists in Agentforce through dual-layer validation (opens in a new tab)

You will learn how to prevent FIELD_INTEGRITY_EXCEPTION errors when Agentforce updates Restricted Picklist fields.

Why read this

The piece outlines a dual-layer strategy combining explicit prompt instructions in the Agent Definition with runtime validation in Lightning Flow.

When Agentforce processes natural language requests to update Restricted Picklist fields, the underlying large language model often passes synonyms or different casing that do not match the exact API names. This mismatch triggers a FIELD_INTEGRITY_EXCEPTION during Flow execution.

The author recommends a dual-layer validation approach to solve this. The first layer occurs at the Agent Definition stage, where developers configure action parameters using structured instructions. These instructions whitelist exact values, define case sensitivity, map common synonyms to valid API names, and direct the model to request clarification instead of guessing invalid inputs.

The second layer enforces checks within the backend Lightning Flow before any record update occurs. By combining strict prompt guardrails with explicit flow logic, practitioners can ensure reliable data ingestion while maintaining the integrity of Restricted Picklist fields.

Read the original at InfallibleTechie (opens in a new tab)

Worth reading?

Must-read

How to voice-enable an Agent Script agent with proven best practices (opens in a new tab)

Readers will learn the exact configuration blocks needed to enable voice in an Agent Script agent and how to adjust system instructions for spoken delivery.

Why read this

The guide also covers org prerequisites and deployment steps to avoid common speech-to-text pitfalls.

  1. Verify Agentforce Voice is active
  2. Insert language, telephony, and modality blocks
  3. Rewrite instructions for spoken delivery
A streamlined workflow to voice-enable an Agent Script agent

Before modifying any code, administrators must verify that Agentforce Voice is active in the organization. Once enabled, adding voice capability follows a straightforward two-part workflow that keeps the core agent logic intact while routing conversations through a telephony channel.

Developers need to insert three specific configuration blocks into their Agent Script files. These blocks define the supported language, establish the telephony connection, and select the outbound voice model along with its persona. The nested settings ensure the correct speech synthesis engine handles both incoming audio transcription and outgoing responses.

Because listeners cannot reread text, the system prompts require careful rewriting. Replies must be concise, free of markdown or raw code snippets, and formatted so symbols are spoken as words. The guide emphasizes training the agent to silently correct common speech-to-text errors, such as mishearing technical terms, before providing a final response.

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

Worth reading?