Change Set Considerations for Prompt Templates

Activate and Deactivate

• Activating a prompt template changes the version status from Draft to Published. When a version is published, it can't be changed to a draft.
• Prompt template versions can be activated or deactivated.
• A version doesn't auto-activate during deployment between multiple orgs unless the Deploy Prompt Templates permission is enabled in the target org. This permission is only applicable to change sets and can be found in Setup under Einstein Setup.
• If the prompt template is in use, a version can't be deactivated unless another version is active.
• If a prompt template is in use, the active version can't be deleted.
• If a flow is referenced in a prompt template and deployed, the flow isn't auto-activated. Follow the flow guidelines for auto-activation. If a prompt template is executed with an inactive flow, you receive an error at runtime.

Activate Prompt Templates on Deploy

A setting in Setup, under Einstein Setup, controls whether active prompt templates in the source org are automatically activated in the target org during change set deployment. This setting is disabled by default.

When this setting is enabled, the deployment follows these rules.

• Prompt templates that are active in the source org are automatically activated in the target org upon deployment.
• Templates that aren't active in the source org are deployed but remain inactive in the target org.

When this setting is disabled, the default behavior applies.

• All deployed templates arrive in the target org but remain inactive, regardless of their activation status in the source org.
• Templates must be manually activated in the target org after deployment.

This setting applies only to change set deployments. It doesn't apply to CLI or package deployments.

Deploy Only the Active Template Version

A setting in Setup, under Einstein, controls whether only the active prompt template version is deployed via change sets. This setting is disabled by default.

When this setting is enabled, the deployment follows these rules.

• Only the active version of each template is included during deployment. All inactive versions are skipped.
• If a template has no active version, the deployment fails with an error.
• Existing versions in the target org are never deleted during deployment.
• If the active version already exists in the target org, these conditions apply.
  • If the version is in draft status, the content is updated and the version is activated.
  • If the version is published, the content isn't modified (published versions are immutable). Only the activation status changes.
• If the active version doesn't exist in the target org, a new version is created and activated.
• If the template doesn't exist in the target org, a new template is created with only the active version.
• This setting works together with the existing Deploy Prompt Templates permission (also under Einstein in Setup) in these ways.
  • If both are enabled, the active version is deployed and auto-activated in the target org.
  • If only Deploy Only Active Version is enabled (Deploy Prompt Templates is disabled), the active version is deployed but isn't auto-activated.
• This setting doesn't apply to managed package scenarios.

When this setting is disabled, the default behavior applies.

• All versions are deployed as they are today. No change in behavior.

Review other considerations

Review these additional considerations.

• Any published prompt template version can't be modified and is skipped when it's deployed.
• If a template is overridden, users can't override it again with a change set, command-line interface (CLI), or Connect API.
• Prompt templates can't be deleted via change set.
• When you deploy a template with custom large language model (LLM) configuration, verify that the target org has a model with the same name. If the model name doesn't match, the deployment fails.
• When a template is deployed by using a change set, all versions—active or inactive—are included in the deployment.
• Add all resources in the change set, and then add dependencies.