Section 2 · Prompt Engineering · 20% of exam
2.5 Creating, Activating, and Executing Prompt Templates
Exam objective
Explain the lifecycle for creating, activating, and executing a prompt template and identify key checks at each stage.
A prompt template moves through design, configuration, testing, activation, and execution. This lifecycle matters because a prompt that has only been drafted is not necessarily available to users or automation. The exam expects you to understand the sequence and the purpose of each stage, including the need to test a template with realistic data before making it active.
Create and configure
Start with a clearly scoped use case and choose the template type that fits its input and output. Give the template a meaningful name and description so administrators can distinguish it later. Associate the required object or field when the type calls for it. Add instructions that define the task, output format, boundaries, and handling of missing information. Insert only the required merge fields and resources. Confirm that each resource is available from the intended execution path and that sensitive data is not unnecessarily included. A good template is not just a natural-language paragraph. It also has configuration: inputs, resource references, model settings where available, and a calling feature such as a record action, Flow, or other supported integration. Validate that the dependencies are available in the target org and that users have the necessary permissions. If the prompt depends on a Flow, confirm its inputs, outputs, and behavior. If it relies on a related list or Data 360, verify that source is connected and returns useful context.
Preview, test, and revise
Use Prompt Builder's preview or test experience with representative records. Inspect the resolved prompt and the output, not just the written instruction. Confirm that merge fields resolve, grounding information appears, output matches the requested format, and the response does not invent unsupported details. Try edge cases such as blank fields, unusually long text, conflicting data, or no retrieval result. Revise the instructions or resource selection, then test again. A single successful example is not enough to show the template is reliable.
Activate and execute
Activation makes a template available through its supported Salesforce use. Before activating, verify that it is the correct version, required inputs and permissions are in place, and the output destination is appropriate. Execution occurs when a user or supported automation invokes the template. At run time, the template receives its input values, combines instructions with grounded context, sends the request through the Salesforce AI layer to the model, and returns generated content to the calling experience. Depending on the feature, the user may review the output or an automation may pass it to another step.
If an active template needs a change, manage that change deliberately. Update the right version, test the new behavior, and coordinate deployment if the template is moving between sandbox and production. Do not assume an edit in a sandbox automatically updates the production template.
Treat activation as a release decision. Test representative inputs and verify the user experience, permissions, and output handling before exposing the template.
Extra concept: Execution can occur through Salesforce features, invocable actions, Connect REST API, or Connect in Apex when supported. The invocation mechanism determines which inputs and permissions must be checked.
Official reference: Salesforce Help, Create a Prompt Template - https://help.salesforce.com/s/articleVie w?id=ai.prompt_builder_build_template.htm&language=en_US&type=5
Key takeaways
- Configure the use case, template type, inputs, resources, and permissions before testing.
- Preview resolved context and revise based on varied test cases.
- Activate only after confirming dependencies and the run-time path.
