A prompt template author has just finished configuring a new field generation template's instructions and grounding. What is the correct next step before the template can be run against a live Case record by end users?
Select an answer to reveal the explanation.
Short Explanation
You’ve finished configuring the template, so your next step is to activate it after the review or testing gate your org requires. Activation is the go-live gate; deleting the draft, skipping activation, or treating Trust Layer masking as a required precondition doesn’t replace it.
Full Explanation
The correct next step is to activate the template after following whatever review or testing gate your org has established. Activation is the lifecycle gate between configuring a template and making it available for execution against a live Case record; completing the instructions and grounding alone does not make the template runnable. Deleting the draft and starting over discards completed work without addressing the next required step. Granting every profile execute access on the assumption that activation is unnecessary is also incorrect: internally built templates are not exempt from activation, and broad access is not a substitute for the activation gate. Requiring Einstein Trust Layer masking rules to be finished before the template can be reviewed, activated, or tested is wrong because it makes masking an absolute prerequisite and delays the actual next step. Masking is an important data-protection consideration, but the stated sequence still calls for activation after the org’s review/testing process. One exam caveat: activation does not mean that every user should automatically receive execution access; make the template available in accordance with the org’s controls. As a practical check, confirm that the template shows as activated and that the intended end users can execute it against a Case record.