Document template lifecycle

The Lifecycle

Transitions Explained

Creation can produce active or inactive customer content. Duplication always produces a new active copy and leaves its source intact. A built-in therefore does not itself change state when copied; the arrow represents creation of the copy.

Usage is derived from current selections. Clearing every reference releases the content for deactivation or deletion. Unit replacements that omit a template choice also release that reference by restoring built-in selection.

What Cannot Happen

Protected built-ins cannot be edited or removed through configuration. Customer kinds are fixed. A selected customer template must remain active and cannot be deleted.

Concurrency and Timing

Reference validation locks the selected template before accepting a new choice. Deactivation and deletion apply their database guards within the mutation transaction. Expected-version edits reject stale saves, and the console does not refresh the loaded editor on window focus.