Lesson 4 of 41 · All lessons
Salesforce Agentforce Specialist
0 of 41 complete
1Exam Overview
  1. 1.1Agentforce Specialist Complete Exam Overview
2Prompt Engineering20%
  1. 2.1When to Use Prompt Builder
  2. 2.2Prompt Template Access Controls
  3. 2.3Field Generation and Flex Prompt Template Types
  4. 2.4Grounding Techniques for Prompt Templates
  5. 2.5Creating, Activating, and Executing Prompt Templates
  6. 2.6Best Practices for Writing Effective Prompts
  7. 2.7Trust Layer Security and Privacy Features
  8. 2.8Managing and Preventing Specific Models from Being Accessed
3Data 360 Fundamentals20%
  1. 3.1Agentforce Data Library
  2. 3.2Data 360 Concepts for Agentforce
  3. 3.3Chunking
  4. 3.4Indexing
  5. 3.5Retrievers
  6. 3.6Choosing a Grounding Approach for a Scenario
4AI Agents35%
  1. 4.1How an Agentforce Agent Works
  2. 4.2Agent Building Blocks and Agent Script
  3. 4.3Hybrid Reasoning and Deterministic Behavior
  4. 4.4Agentforce Builder: Canvas and Script Views
  5. 4.5Filters, Variables, and Template Expressions
  6. 4.6Standard and Custom Topics
  7. 4.7Standard and Custom Agent Actions
  8. 4.8Configure Topics, Instructions, and Actions for a Use Case
  9. 4.9Connecting Agents to Digital Experience, Email, Voice, and Slack
  10. 4.10Agent Security Context and Action Execution
  11. 4.11Choosing Between Employee and Service Agents
  12. 4.12When to Use Agent API
5Testing, Deployment, and Maintenance10%
  1. 5.1Testing Agents with Testing Center
  2. 5.2Understanding Testing Center Evaluations
  3. 5.3Deploying Agents from Sandbox to Production
  4. 5.4Deploying Prompt Templates Between Environments
  5. 5.5Reviewing Agent Behavior After Changes
6Governance and Observability10%
  1. 6.1Managing and Monitoring Agents
  2. 6.2Agent Analytics and Performance Signals
  3. 6.3Identifying Opportunities to Optimize Agent Behavior
  4. 6.4Using Observations to Guide Improvements
7Multi-Agent Orchestration5%
  1. 7.1Choosing a Multi-Agent Architecture
  2. 7.2Orchestrators and Connected Subagents
  3. 7.3Handoff and Supervisor Modes
  4. 7.4Model Context Protocol (MCP)
  5. 7.5Agent-to-Agent (A2A) Communication

Section 2 · Prompt Engineering · 20% of exam

2.3 Field Generation and Flex Prompt Template Types

4 min read Updated Nov 16, 2026

Exam objective

Given a use case, identify when a Field Generation template or a Flex template is appropriate and recognize its input and output considerations.

Prompt template type determines how a prompt is configured and how its inputs and output fit into Salesforce. The exam guide specifically names Field Generation and Flex types. Choose the type from the use case's input shape, destination, and invocation pattern. A template type is not merely a label; it establishes a workflow for how Salesforce supplies context and uses generated text.

Field Generation templates

A Field Generation prompt template is designed to generate content for a specific field on a Salesforce record. The template is associated with an object and a target field. A user can invoke it from a supported record interface, and the generated response can populate that field for review or saving. This fits use cases such as drafting a description, creating a concise case summary, or suggesting a value for a text field based on the current record context.

The direct connection to a record field is useful when the output belongs in a known place on that record. The administrator should confirm that the field can hold the expected output, the selected object is correct, and users understand whether the generated text is a draft or an automatically saved value. A field-generation template should not be selected just because the prompt needs CRM context; its record-and-field behavior must match the desired workflow.

Flex templates

A Flex prompt template supports custom use cases whose input resources do not fit the predefined structure of another template type. The builder defines the inputs needed for the template, which can involve different Salesforce objects or resources. Salesforce Trailhead describes Flex templates as allowing up to five inputs, while current product behavior and available resources can change, so administrators should verify the current limit in the org and exam documentation. Flex is useful when a prompt needs a custom combination of information, such as account, contact, and product data, or when a Flow will pass different resources to a tailored generation task.

Flex offers flexibility, but the builder must define what each input represents and how it is used. Inputs should be named and described clearly so the resource picker and template instructions are understandable. Confirm that all required inputs are provided by the invocation method. If the template is called from Flow, ensure Flow supplies every required value. If different channels invoke the template, test each path because the available inputs and user experience may differ.

Selecting between them

Choose Field Generation when the requirement is to generate a value for a specific record field through the supported field-generation experience. Choose Flex when the task needs custom inputs or a use case not covered by a predefined template type. If the requirement is a standard Salesforce feature with a dedicated template type, consider that built-in type rather than forcing the work into Flex.

Ask two questions: where should the output go, and how many or what kinds of inputs does the prompt need? A specific record field points toward Field Generation; custom input design points toward Flex.

Generated output may still require user review. Confirm whether the product experience places a person between generation and save, or whether automation writes the output directly.

Extra concept: A Flow can call a prompt template, allowing generated language to participate in a larger automation. Keep control rules and exact updates in the deterministic parts of the Flow.

Official references: Field Generation - https://help.salesforce.com/s/articleView?id=sf.prompt_builder_c reate_field_gen_prompt_template.htm&language=en_US&type=5 | Flex - https://help.salesforce.com/s/a rticleView?id=ai.prompt_builder_create_flex_prompt_template.htm&language=en_US&type=5

Key takeaways

  • Field Generation is tied to populating a selected record field.
  • Flex is for custom use cases with builder-defined inputs.
  • Verify input availability, output destination, and review behavior in the actual invocation path.

Check your knowledge

Answer exam-style Prompt Engineering questions with answers and explanations.

Practice Prompt Engineering
Finished this lesson? Mark it complete to track your progress.

Ready for the real exam?

Take the timed Salesforce Agentforce Specialist simulator: same number of questions, same time limit.

Get Complete Access