Table of Contents


  1. Version 6.4.3
  2. Version 6.4 HotFix 2
  3. Version 6.4 HotFix 1
  4. Version 6.4
  5. Version 6.3
  6. Version 6.2 Hot Fix 2
  7. Version 6.2 Hot Fix 1
  8. Version 6.2
  9. Version 6.1.1
  10. Version 6.1



Effective in version 6.1, the performance and scalability of a purge job has been improved in the following ways:
  • You can resume a purge job from the point of failure.
    Previously, when you resumed a purge job, the job restarted.
  • A new optional parameter called Entity, has been added to the Purge Expired Records job. You can select an entity from the Entity list-of-values window to limit the purge process to an entity in the archive folder.
    Previously, you could narrow the scope of a purge job to all entities you had permission to access.
  • The retention-expiration date is applied to individual tables when a retention policy is applied. Purge jobs are executed more quickly because there is no need for the retention status of individual child records to be first evaluated.
    Previously, the retention-expiration date was set at the driving table. When a purge job was scheduled, the retention status of each child record would be evaluated.

Updated July 03, 2018