Retention limitations and constraints

There are limitations and constraints relating to retention and the system clock. There are also constraints for setting retention on the Snaplock fixed content device.

Limitations and constraints

• You can apply retention only to the following objects and classes: documents, annotations, custom objects, and folders.
• You can increase the retention setting for an object, and you can decrease the retention setting if the AllowRetentionReduction property is set to a value of RetentionReductionAllow. For more information, see Updating object retention with sweeps.
• To prevent tampering with the system clock, Content Platform Engine periodically compares the local system clock to the RDBMS clock. If the clocks are out of sync by 24 hours or more, object deletion requests might fail.
• Indefinite retention is not supported on the Snaplock fixed content device.
• Retention settings can be applied independently to related objects. Retention uses the cascade deletion rule that prevents deletion of an object if an associated object cannot be deleted. For example, a document can have a retention setting and an associated annotation can have a different retention setting. In this case, the cascade deletion rule prevents the document from being deleted if the associated annotation cannot be deleted.