Skip to main content

Version Control

How are versions controlled through publishing new versions, creating future states and keeping track of historical versions

Written by Hylet Pistorius

Each process in the system is assigned a version number. A version number is a unique identifier assigned to a specific state of a process or document. It shows how many times the item has been updated or revised and helps track its history.

For example:

  • 1.0 – the first published version

  • 1.1 – a minor update

  • 2.0 – the next publish

Version numbers allow users to know which version is current, see past versions, and restore earlier versions if needed. Version control is managed through several mechanisms. To read more about each item, select the provided links within the below information.

Publish

When a new version is published, the version number automatically increases, and the previous version is saved in history. This ensures that both the latest and past versions remain accessible for reference.

Auto Version History

The system automatically tracks changes. Whenever decisions or activities are updated, the version number increases, and the previous version is stored in history.

Future States

Users can create a future state version to update a process while keeping the current version accessible. This allows changes to be prepared without disrupting the live process. Once the process is published, the version number will automatically increase.

Offline

When an offline process is reinstated, its version number moves to the next whole number and requires republishing.

History

Previous versions can be restored if necessary, providing a reliable way to revert changes. This approach ensures processes remain flexible, history is preserved, and updates can be managed confidently.

Did this answer your question?