Question 430
At Juniper Civic, a public agency service counter is improving permit status while preparing a production promotion (SF-P15-01). The administrator observes that template preview looks correct as text but the actual resolved prompt lacks the latest case comment. Any fix must ensure that citizen information stays limited to the relevant case. Which underlying Agentforce or Salesforce design principle explains the appropriate approach?
Explanation
Correct Answer
The governing distinction is: Prompt instructions and resolved data are distinct; both affect the final output. In this permit status scenario, this separates supported agent behavior from assumptions about the AI model. Because template preview looks correct as text but the actual resolved prompt lacks the latest case comment, the intended response is to inspect resolved prompt resources and test with a case whose comments changed after setup. An observable check is that preview shows the new case comment in the resolved input before response generation.
Incorrect Answers
The idea “A saved draft is not necessarily the active executable prompt template version; interpret this without inferring extra permissions from an LLM response” explains another source-defined situation: A team saves edited prompt instructions but production still executes an older template version. The correction must ensure that guest profile fields are used only with permitted access. That situation depends on: A saved draft is not necessarily the active executable prompt template version. The present question instead concerns template preview looks correct as text but the actual resolved prompt lacks the latest case comment. The correction must ensure that citizen information stays limited to the relevant case. Its directly relevant mechanism is: Prompt instructions and resolved data are distinct; both affect the final output.
The idea “A template invocation depends on correct input bindings and execution context; interpret this as distinct from unrelated UI configuration” explains another source-defined situation: A Flow invokes a prompt template without supplying the record inputs expected by its definition. The correction must ensure that escalations preserve only the needed guest context. That situation depends on: A template invocation depends on correct input bindings and execution context. The present question instead concerns template preview looks correct as text but the actual resolved prompt lacks the latest case comment. The correction must ensure that citizen information stays limited to the relevant case. Its directly relevant mechanism is: Prompt instructions and resolved data are distinct; both affect the final output.
The idea “Conflicting directions undermine deterministic expectations and reliable evaluation; interpret this as a necessary control for deterministic outcomes” explains another source-defined situation: A template tells the model to use only current CRM values but also to invent friendly dates for empty fields. The correction must ensure that donor details cannot be revealed across accounts. That situation depends on: Conflicting directions undermine deterministic expectations and reliable evaluation. The present question instead concerns template preview looks correct as text but the actual resolved prompt lacks the latest case comment. The correction must ensure that citizen information stays limited to the relevant case. Its directly relevant mechanism is: Prompt instructions and resolved data are distinct; both affect the final output.