Configuring automatic version purging

The automatic purge feature allows DOQMIND to clean up old asset versions on a nightly schedule. It is configured in Administration → Assets → Purge versions.

Enabling automatic purging

By default, automatic purging is disabled. To enable it, toggle the Automatic purge setting to on. When disabled, all other settings in this section are grayed out and inactive. When enabled, the remaining settings become mandatory.

Purge settings

Once automatic purging is enabled, two thresholds must be configured:

Purge versions older than [X] days
Versions older than the specified number of days will be candidates for purging. The minimum value is 7 days; there is no maximum.

Keep at least [Y] versions
Regardless of age, this many versions will always be retained per asset. The minimum value is 1; there is no maximum.

How the two thresholds interact

Both conditions must be satisfied for a version to be purged. A version is only purged if:

• it is older than the configured number of days, and

• removing it would still leave at least the configured minimum number of versions on the asset.

For example: if the threshold is set to purge versions older than 30 days, but an asset has only 2 versions and the minimum is set to 2, neither version will be purged — even if both are older than 30 days.

When does the purge run?

The automatic purge runs once per night. There is no manual trigger for the scheduled purge; if you need to remove a specific version immediately, use manual purging instead (see Purging asset versions).

Purge history in the audit log

When a version is purged automatically, a history entry is added to the asset's Logs tab. The entry reads: Version [X] was purged automatically, with a timestamp. No user is attributed to automatic purge entries.