Developer Fundamentals27% of the exam
Agentforce for Developers: use cases and limits
What the Agentforce for Developers IDE assistant can and cannot do (Dev Assistant slash commands, inline autocomplete, metadata grounding, trust and review), plus the developer's side of Agentforce: invocable Apex and flow agent actions, Apex in Prompt Builder and the limits of Testing Center.
Understand use cases and limitations of using Agentforce for Developers.
~8 min read · 12 practice questions ·
What the exam expects
- Pick the tasks Dev Assistant handles in the IDE (generate, explain, test, document code) and those it does not (deploy, merge, build agents).
- Explain where the tool runs, how it grounds suggestions and how it protects your code.
- State its limits: generated code needs human review and the normal deployment rules.
- Expose Apex and flows to agents as custom actions and to Prompt Builder as resources.
- Know Testing Center's purpose and limits.
Key terms: Dev Assistant is the chat assistant in Agentforce for Developers; a slash command is a preconfigured prompt such as /test; grounding (RAG) adds your project's metadata to the prompt; an agent action is a tool an agent can run.
Key facts
Where it runs
- Detail
- VS Code desktop and Code Builder, via the Salesforce Extension Pack (Expanded)
Built-in slash commands
- Detail
/explain,/test,/document; plain natural language also works
Grounding
- Detail
- RAG over current schema and metadata in the local project
Training and trust
- Detail
- Customer code never trains the models; responses are masked and toxicity-checked
Review
- Detail
- Salesforce recommends code review for all AI-generated code
Custom action sources
- Detail
- Invocable and REST Apex, external services, autolaunched flows, MuleSoft APIs, prompt templates
Agent Apex bulkification
- Detail
- Not bulkified by default; each action runs in its own transaction
Prompt template Apex
- Detail
List<Request>in (first element only),List<Response>withPromptout
Testing Center limits
- Detail
- Up to 10 test jobs in 10 hours; up to 1000 test cases per test
Testing Center environment
- Detail
- Sandbox only, because tests can modify CRM data
Sources for this section (6)
- Introducing Agentforce for Developersdeveloper.salesforce.com (opens in a new tab)
- Create a Custom Agent Action in the Legacy Builderhelp.salesforce.com (opens in a new tab)
- Best Practices for Building Agentforce Apex Actionsdeveloper.salesforce.com (opens in a new tab)
- Grounding with Apex Merge Fieldshelp.salesforce.com (opens in a new tab)
- Trust Your Agentstrailhead.salesforce.com (opens in a new tab)
- Agentforce Testing Centerhelp.salesforce.com (opens in a new tab)
- Why do Dev Assistant suggestions reference the org's own custom fields?
- Why should an invocable method used as an agent action have a clear label and description?
- When should you use Testing Center instead of testing in Agent Builder?
- Which input does an Apex class used as a prompt template resource receive?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Platform Developer pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 21 lessons of the Platform Developer guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (12 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams