HelpServer’s versioning system saves and restores older copies of active (i.e. published) content. The idea is to revert to content at a point in the past or to show or to prove exactly what the content was on a particular day, which is, for example, a requirement for legal services.
The final state in the life-cycle of a content object is called ‘Active’ and it is produced by the publish function. In the 'Active' state, an object is assumed to be ready for use and only when a content object is in that state you can fix it into a new version.
When you create a new version the active object instance of that moment becomes old or 'Inactive'. Inactive object instances cannot be changed and are read-only. This means that after fixing content in a version you can change and publish the content without affecting the versioned instances.
Users see the active instance of an object by default, but they they can browse the inactive (older) instances.
Authors always work on the 'Latest' object instance and they use can the view mode function to switch to the inactive object instances in order to preview, restore, or remove them.
Versioning is distinct from a backup system. A backup system creates copies of the complete repository while a versioning system creates copies of specific content objects that have changed and released to the user community.
Versioning overlaps revisioning, but revisioning is more granular. Each change is marked and undoable while versioning includes a set of changes in relation to an object’s life cycle.