Revision Biased Links

[woodstylee3]

It would be very useful for us to be able to 

1)  Create Links to Historic Revisions of files

2) Create Links that do not automatically show the latest revisions of files.

This comes from use cases where we stores copies of customers standards in vault. Our projects are varied in length, and not all customers will use the latest revisions of standards on all projects. Projects may need to keep a reference to the revisions of the standards they worked to. 

As links always reflects the latest revision, we tend to copy the documents into each project and struggle to centralise them, which is not great.

Proposal is to allow drag drop from history grid to create historic links, or standard behaviour to create "current behaviour links", and to show the triangle icon in the file grid, when it is out of date. Handling of updating the link, by deleting and recreating the link.

[ihayesjr]

@woodstylee3 

Thank you for posting the idea. When you finish a project, are you locking the folder and files inside of that folder locked with the latest revision?

[woodstylee3]

Our files are under Rev control in file lifecycles, which are locked when released, and folders are locked when project finishes. I've not tested what happens to links to folders outside of the folder hierarchy when we do that. However the desired behaviour may be needed whilst both project are live. (For example project A issues a file at Rev 1, Project B issues the same file at Rev 2). But project A team continues based on Rev 1 of the spec issued.

We tend to copy the files multiple places around the vault at moment, as the default behaviour of links is to auto show the latest revision, and have not tested what happens to links inside a locked folder. But can setup a test for this and post the results. 

[ihayesjr]

If you users on Project A get a Top level assembly that uses Rev 1 of the part, you don't need a link. Users can pull the correct revisions by making sure they perform a Get on the Revision.

[woodstylee3]

Hi Irvin, our query is not related to CAD data , we are using Vault Office extensively within the business. as well as Vault Pro.

And links primarily of use on specification (pdf, word, excel) .

However releasing models with old revision parts may also be a seperate Idea.

[woodstylee3]

I'm quite convinced the default behaviour of links is version specific already, in that it seems to retrieve the Version Id not the master Id on the links.