Skip to main content

Template Versioning

Manage template versions to track changes, maintain compatibility, and allow rollback if needed.

Version Numbering​

Templates use semantic versioning: Major.Minor.Patch

1.0.0  →  First release
1.1.0  →  New field added (minor change)
1.0.1  →  Bug fix (patch)
2.0.0  →  Major restructure

Creating Versions​

When you update a template:

  1. Modify template
  2. Increment version number
  3. Add change notes
  4. Publish new version

Version Management​

note

Publishing a new template version does not change existing cases — they keep their current version. Existing cases are only updated if you initiate a migration.

Viewing Versions​

  • See all past versions
  • View what changed
  • Compare with previous
  • See usage counts

Switching Versions​

  • New cases use latest
  • Existing cases keep current
  • Migration options available
  • Compatibility checked

Deprecation​

Mark old versions as deprecated:

  • Still available for reference
  • Not recommended for new cases
  • Clear migration path
  • Scheduled removal date

Change Tracking​

Each version records:

  • Changed by — Who made changes
  • Date published — When released
  • Notes — What changed and why
  • Fields added — New fields
  • Fields removed — Deleted fields
  • Fields modified — Updated fields

Migration​

When updating existing cases:

  • Automatic — Use new version
  • Manual — Review before update
  • Scheduled — Update at specific time
  • Conditional — Only if certain fields empty

Best Practices​

  • Add clear change notes
  • Plan major changes carefully
  • Test versions before publishing
  • Deprecate old versions gradually
  • Document breaking changes
  • Communicate updates to team
  • Keep version history

Rollback​

If needed, rollback to previous version:

  1. Open template
  2. Select version
  3. Click Rollback
  4. Confirm change

Existing cases on new version unchanged.

See Also​