Library folders are supposed to protect files from change. This works great as long as the files stay in the library folder. However, if you drag a file out of the library folder and, say, into the designs folder, the file is no longer protected (marked as read only). The only way to prevent files from being moved out of a library folder is to modify the access permissions to read only. The problem with doing this is that you can no longer add files to the library. Users need to add files to the library on a regular basis, and therefore we cannot ask that an administrator be required to do this.
Am I understanding this correctly??? If so...I'm absolutely amazed that this is the case. In otherwords, you really can't put your trust into a library file being unmodified.
Is there another way to allow average users to create library files, add them to a library (that they may create), and protect those files from future (inadvertant) change? Sure, you can limit security on the folder to only allow the admin modify priveleges, but this also means that an average user won't be able to add a file.
Another interesting thing I've discoverd is that you can revert to previous versions of library files without ever even moving the files out of the library. Here is how:
1. Check out the latest version of the library file from Vault.
2. In the history browser, right click on a previous version and select "Get/Checkout" (the checkout box is already checked because it is already checked out to you, and gray because it is a previous version). By the way, I'm using Vault Professional and there is no way to list versions on checkout.
3. Check back in the file using Inventor (because, for us at least, Inventor files must be checked in using Inventor).
Bam, library file has been changed and all associated assemblies have been affected....NOT GOOD.
This sounds like the software is behaving as it is supposed to.
I have put in a request with development on your behalf to improve the documentation in the Vault client surrounding how library files behave.
i wonder if you were to consider to;
-make a lifecycle state called " admin locked".
-when you have library files that you are happy with, then put them in this state.
-make permission for this state security, read (no modify, no delete) for your main design staff.
so from time to time when you deem a set of files to be good to go, just move them into this state.
make the admins and power users have modify and delete if you want.
not sure if the move to different folder to cheat the system will then be as easy. let me know how it goes please. i will do a test myself when i can.
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register
Start with some of our most frequented solutions to get help installing your software.