File control - set purge settings into force reactively

[Markus.Koechl]

Quite frequently purge control settings got no attention during Vault implementation. Later customers recognize that their Vault maintains much more file versions than necessary. Changes to the version control are applied to future file versions created, but not set into force reactively for existing vaulted data. Therefore I'd appreciate (speaking for several customers 😉 ) to get an option to change purge flags for existing files also.

[bernd05]

If I change the purge configuration in the lifecycle, these changes don't occur in the purge process at filesversions created in the past.
There should be a possibility to purge all filesversions with the new purge configuration.

[Anonymous]

Fully support this requirement.

With current purge logic we cannot purge at all, since it is not possible to predict what gets purged (who knows what purge configurations have been valid over the years)

There are strict rules what we are allowed to purge and need control over the purge of old versions.

[Patrick.De.Neef]

Now the standard purge follows the rules defined in the lifecycle assigned to the file

for files not having a lifecycle you can define the number of versions to keep, when purging files with a lifecycle manually it would be benificial to have this option also to allow overwritingthe settings in the lifecycle

[RajSchmidt]

If I ever change the purge rules of an existing lifecycle these rules will be applied to new files. Old versions of existing files however stick to the old rules. Quite often you start out with some legacy data base which has not been configured properly. In these cases it becomes almost impossible to get rid of old stuff.

Please apply new purge rules to existing versions.

[Senthil_Kumar]

This is implemented in Vault 2021. For more info on Vault 2021 What's new please refer this page - What's New in Vault 2021