COMAND Version Control

Version control maintains an audit trail, can be used to control modifications across content records and fields, and can be enabled per content type and folder to maintain an archive of past revisions for audit, access and roll-back.

Audit Trail

Each time a content record is created or modified, information about the author and time of modification is recorded. Modification notes can optionally be included as well. An audit trail is maintained regardless of version control settings. Past audit trail information may be automatically deleted after a configured limit on the number of audit trail entries, removing the oldest information across an entire repository first.

Locking

In addition to a revision archive, version control also provides a mechenism to restrict modification of the fields of one or more content records to a single user. This is useful when collaboration is not desired, such as when a batch of updates across multiple fields or content records should be managed by a single user. A similar feature in other systems include file locking, record locking or "check-in" and "check-out".

Revisions

Each time a version controlled content record is modified, the previous revision is retained in the repository. Each revision includes information about the author and time of modification.

Revision history is enabled per content type and folder, and can be limited to a specific number of revisions.

Storage Scheme

Audit trail and lock information is stored outside of content records, in a repository's Content Log.

Revisions are stored as additional content records with metadata to identify the record as a revision and associate it with the active content record. For more technical information, see Relational Database Content Active ID column.