A hold prevents content from being accidentally altered or deleted. Previously scheduled destruction or disposition of the data is suspended until the hold is released.
When a federated document is declared as a record, the content must be placed under a retention hold, even though the content resides in the Content Manager OnDemand repository. The document content in Content Manager OnDemand is placed under a retention hold such that the content can be deleted by IBM® Enterprise Records only. There are two ways to place a retention hold on Content Federation Services for Content Manager OnDemand documents.
By using the Enhanced Retention Management feature of Content Manager OnDemand, you can configure an application group to place a hold on the source documents. The source Content Manager OnDemand documents are simultaneously federated and locked down in Content Manager OnDemand. The federated Content Manager OnDemand documents are not yet under the control of IBM Enterprise Records. To ensure that the retention hold is controlled by IBM Enterprise Records, you must use IBM Enterprise Records to declare the federated Content Manager OnDemand documents as records within Content Platform Engine.
The following sequence of illustrations describes this process.
You can federate the Content Manager OnDemand documents to Content Platform Engine by using Content Federation Services for Content Manager OnDemand and later use IBM Enterprise Records to declare the federated documents in Content Platform Engine as records. This action causes the Content Manager OnDemand system to place a hold on the source documents in the Content Manager OnDemand server. The following sequence of illustrations describes this process.