Save
One of those painful messes we find ourselves in from
time to time is a local file that is both locked and modified?!?
We manage to get something like an assembly file on our local drive and it needs to update its references based on the project or the wrong file version or revision being referenced, perhaps we have edited the open file even though we were warned not to, so its marked
as needing to be saved.
No problem, just check it out and save right? No, not so fast, it’s locked in a released state.
Well I’ll just change the state right? Nope, Vault doesn't like that either.
So typically we have 2 options – get the last effective revision (losing any changes and wrestling with revision bias) so I can change state OR we could go to Vault Explorer, change the state and check it
out, then reopen in Inventor and do our updates, either way we are burning needless time and effort to get our assembly back on track.
No longer – in 2014 we can now change the state on locally modified
files; so what does this mean?
Instead of closing files, losing changes or going back to Vault Explorer, we can change state on these files marked as requiring save and retain all the
local edits! Once the state is changed you can simply check out your file, save and check back in – this simple change is hoped will make life with the Inventor add in much more bearable for those using document lifecycle management.
-Allan
Photo: Dawn Perry
