Versioning

Versioning

You can create different versions of content to maintain a history of changes and to control which users can change the content at a given time. The set of versions for a single document is called a version series. Content Engine supports a two-level versioning scheme, in which a document version is either a major or minor version. Minor versions typically denote an “in-progress” document, whereas a major version typically denotes a completed document. In addition to version numbers, the system maintains a state property indicating the current state of each version of the document, as follows:
 
In Process – A work in progress version. Only one version of a version series can be in this state.
 
Reservation – A document currently checked out for modification. Only the latest version of a version series can be in this state.
 
Released – A document released as a major version. Only one major version of a version series can be in this state.
 
Superseded – A version superseded by another version. Many versions in the version series can be superseded.

Additional capabilities in the versioning model include the following:

1. The system can be configured to apply security policies that in turn automatically apply different access rights for major and minor versions, making it easy to enforce a different viewing audience for inprogress documents.
2. A document can be promoted from a minor to a major version without requiring the content to be versioned.
3. A document can be demoted from a major version to a minor version, which is useful if the document has incorrectly been promoted to a major version.
4. A document can be saved to the object store prior to being checked in. By doing so, users can avoid keeping content on their local systems, and multiple users can work on a checked-out document.
5. Versioning can be enabled and disabled on a document class level for cases when multiple versions are not required.
6. A version can be frozen so that the custom properties associated with it cannot be changed.
7. Users or administrators can view all versions in their respective user interfaces.
8. Versions can be deleted.