You will see both versions and revisions while working on templates. A version selects the template edition to use; revisions record changes within that edition. Together, they let you develop a design and trace its saved content.
1. Versions select what to run
A template can have v1, v2, and subsequent versions. Each has its own content and Draft/Published status. Run lets you select the version before creating a PDF.
For an integration, specify version to target the intended edition. If omitted, the system uses the template’s current version, which does not necessarily mean the latest published version.
2. Revisions record changes within a version
Saved content is recorded as a revision that you can inspect or restore. For example, v2 may have revision 1 at creation, revision 2 for a content edit, and revision 3 for a CSS change.
A revision number does not replace the version in Run. Selecting v2 does not pin an immutable revision either: v2 can still receive further saves.
3. Create a version from an existing one or start blank
Open the version selector in the top bar and choose New version. Select a source version and choose Create to reuse its design, or choose Blank to start empty.
Wait for creation to finish before editing. The new version needs its own review and publication; requests targeting the old number continue to do so until you change them.
4. Distinguish version, variant, and schemaVersion
These names refer to different choices:
| Name | Purpose |
|---|---|
| Version | Template edition selected for a PDF job. |
| Variant | Alternative values or visibility within a version. |
schemaVersion |
Template data format in its JSON file. |
For alternative labels or colors within a shared structure, see Variants. To return to an earlier save, use revision history.