Keeping unstructured documents pruned to a certain number can save significant disk space, depending on the number and size of the unstructured documents.
Older versions of unstructured documents can be deleted from the repository by a pruning job to save disk space.
Pruning can be enabled or disabled at the cabinet or folder level by attaching a custom attribute. See Using Custom Attributes to Skip Retailer Processing of Cabinets or Folders. An administrator can also enable or disable pruning at the repository level. See the task Enabling or Disabling Unstructured Document Pruning in the CMS Installation and Configuration Guide.
When pruning is enabled, you can set a pruning policy on property sheets for finer control at various levels in the repository. See Unstructured File Pruning Policy.
Pruning is done asynchronously to the checkin event that created a new version of the file. Pruning is performed by the batch process that also indexes the file.