Content Services repositories can archive older versions of documents. Because version archival causes content to become temporarily or even permanently unavailable, archived documents cannot be locked down and thus cannot be declared as records.
Documents can be archived manually or they can be automatically archived by setting a version threshold such that when a new version is created and the total versions exceed the threshold, the oldest version is archived.
When a version of a Content Services document is federated, Content Platform Engine updates the source version in Content Services and sets the Permanent Version flag. Setting the Permanent Version flag exempts a document from automatic archival but it does not prevent manual archival. Content Platform Engine cannot prevent the Permanent Version flag from being updated by using native Content Services applications. For document versions that were already federated, avoid manually archiving the documents and avoid resetting the PermanentVersion flag to false.