Vault Purge - Enhancement to remove unwanted versions

[karthur1]

I would like to see the Purge command enhanced so that it would allow files with dependent parents to be purged.  The way that it is now, the file can't be purged (sometimes not even when the "unconditional purge" is checked) until after the dependent parent is purged.  This can be difficult (sometimes impossible) and time consuming to track down because of all the related dependencies of the vaulted files.

What I think would be helpful is to have the option to replace the version in the parent with the "latest" version of the file. Then the older versions can be purged out and there will not be any missing references when the assembly is later opened in Inventor.

Thanks

[ihayesjr]

@karthur1 

Is this still an issue for you?

[karthur1]

Currently using Vault Pro 2022. I haven't tried it in a while. Has there been changes to help with this?

[ihayesjr]

We have made lots of changes in the product since you originally posted this that might effect this workflow. That is what I asking if this is still an issue.

[nselles-alvarez]

Please allow admins the ability to purge all but the latest version of multiple files, overriding all restrictions. On my hands and knees begging.

[ihayesjr]

@nselles-alvarez 

Are you using lifecycle definitions on your files?

[nselles-alvarez]

Not yet and yes.

Not yet: I am preparing Vault for the engineers (such as myself) to use. However prior to use, I have to upload many thousands of record drawings. Each time I alter the file's category, state, lifecycle definition, attach UDP, Vault creates a new version. Now that I have the old records the way I want them, I want to purge all the versions that it took to get the final version, prior to releasing Vault to the engineers as a ready to use file management and life cycle management solution.

How to do so?

[karthur1]

@ihayesjr  wrote :

We have made lots of changes in the product since you originally posted this that might effect this workflow. That is what I asking if this is still an issue.

Using Vault Pro 2022. Nothing has changed with this. Still can't purge because of Vault restrictions is in my original post.  I do not use lifecycle definitions.  This is mainly because I do not know what it would affect and because I do not know how.

Thanks

[karthur1]

Using Vault Pro 2022. Nothing has changed with this. Still can't purge because of Vault restrictions is in my original post.  I do not use lifecycle definitions.  This is mainly because I do not know what it would affect and because I do not know how.

[karthur1]

Thanks

[ihayesjr]

@karthur1 

We would most likely not make a change to remove children with a dependent parent. It would break the parent.

It also wouldn't be advised to replace the child during the purge process.

Lifecycle Definitions would help because the purge process is based on the revision and not on the version.

Therefore, if you had 10 versions in WIP and set it to keep the first and last version, Vault could purge versions 2-9 regardless of the parent and it kept version 1 and 10.

@nselles-alvarez why are you changing the lifecycle definition on the file? If you kept the same definition, the file could purged based on the state control settings.

[ihayesjr]

@karthur1 

Also, have you tried purging at the Vault level and not at the File level?

Your image is based on a particular part. If you purged at the Vault level, it would purge the parent first then it could purge versions of the file. 

Running the purge on the Vault Server will generate a report where you can look at all of the files that are candidates to be purged. You can review this report before running the purge so you get an understanding of what the process is going to look at. Also, post purge, there is a report to tell you what was purged.

[mrdelicious2]

"What I think would be helpful is to have the option to replace the version in the parent with the "latest" version of the file. Then the older versions can be purged out and there will not be any missing references when the assembly is later opened in Inventor."

I was just thinking this exact statement and found topic w/ search.  It would be nice to be able to do this and delete other versions that the only meaningful difference is irrelevant.  Re-Point and exsisting drawing to the latest or different version of the model.