As described in Versioning an Asset, CentraSite automatically maintains an internal version number for each asset. The version number has the format <MajorVersion>.<Revision>, for example, 2.0.

When revision processing is enabled, the revision number of an asset is initially 1 and is automatically incremented each time you save changes to the asset. When revision processing is disabled, all revisions of an asset except the most recent are discarded and the revision number is automatically reset to 0.

When you create a new version of an asset, CentraSite internally treats the new asset version as a new registry object and assigns a new internal object ID to it. When you create a new revision of an asset, CentraSite internally treats the new asset revision as the same registry object and does not assign a new internal object ID to it.

Currently, when you switch the revision feature on or off, you can only do this for all assets in all organizations; there is no possibility of limiting the effects of revision processing to a subset of the assets or organizations.

By default, that is, immediately after the installation of CentraSite, revision processing is switched off.

Deleting an object also deletes all of its revisions. The constraints for deleting objects however apply only to the current revision. This means that all incoming associations that exist on the current state of the object have to be released before deletion.

If an object with existing revisions is exported, then only the currently selected revision is exported and the revision history is not exported.

Searching (including Advanced Search) always defaults to the current revision of an object. It is possible to express a revision label in an advanced search. If an advanced search expects revisions to be found, it is not possible to define additional search criteria.