The record deletion process differs depending on whether the federated Content Manager OnDemand documents are declared as records within Content Platform Engine.
When the federated Content Manager OnDemand documents
are declared as records, Content Manager OnDemand places
a hold on the source document. Content Manager OnDemand also
excludes the source document from the deletion process even if the
expiration date for the source document is reached.
The following scenarios describe the delete behaviors for the federated
and source Content Manager OnDemand documents:
- Federated Content Manager OnDemand documents that are not declared as records,
and ready for deletion from Content Platform Engine
- The federated Content Manager OnDemand documents are deleted from Content Platform Engine. The corresponding source documents in Content Manager OnDemand are not deleted until their expiration date is reached.
- Federated Content Manager OnDemand documents that are not declared as records
but exist in Content Platform Engine and the expiration date for the source
Content Manager OnDemand documents is reached
- The Content Manager OnDemand server generates a delete request for Content Platform Engine, which deletes the federated Content Manager OnDemand documents from Content Platform Engine.
- Federated Content Manager OnDemand documents that are declared as records and
ready for deletion
- When the records are deleted from IBM® Enterprise Records, the source
documents are deleted immediately, regardless of the expiration date on the source documents in
Content Manager OnDemand.