Drafts, versions and activation
Template bodies and layouts have version histories. Saving, cloning and activating perform different operations.


| Action | Result |
|---|---|
| Save a new template/layout | Create the item and its first draft version |
| Save a loaded draft | Update that draft's content; do not create a new version each time |
| Clone a version | Create a new draft version from the current editor content |
| Activate a version | Make that version the active published choice |
| Load a version | Inspect/select its content in the editor; loading alone does not activate it |
| Clone a template from the list | Start a separate template with its own code and identity |
Publish a controlled revision
- Open the template's Versions tab.
- Identify the loaded version and the Active/Draft/Published indicators.
- For a published or active body, choose Clone v… to create an editable draft.
- Edit and Save the draft. Review the body, Input JSON, metadata and layout.
- Preview the result with representative values.
- Choose Activate v… for the version approved for use.
- Check the list's version badge and Generate output.
Published/active bodies are immutable. Editing a template's descriptive settings is separate from rewriting its published body. If a body save is refused, clone it to a draft instead of repeatedly retrying the published version.
Select an earlier design
Load and review the earlier version, then activate it when that is the desired change. Later drafts remain distinct from the selected active version. Check the layout's active version too: a correct body combined with an unintended layout can still produce an unexpected document.
A browser preview can include unsaved content. Do not treat it as proof that the saved active version has changed.