Save
Last post we discussed the Replace command in Vault and it’s benefits. For review, we took an Inventor assembly that was a subassembly in a larger context, and replaced it with another. See the before and after images below:
Before the Replace command:
After the Replace command:
Wait, what happened to the original file? And how did that Obsolete state get there? In my example, there are no more direct parents to that FRP-1.iam file. You have an 'orphaned' file on your hands. Now what to do with that file…
There are a variety of scenarios here, let's take the one where a component is bad – really bad – and you need to remove it from production use. This file should be kept around in Vault however, and the Obsolete lifecycle state is just the thing for the job.
Next, the Lifecycle definition that is used on that file should have the Obsolete Lifecycle state configured properly. Ideally this means access to it will be limited to Administrators in a read-only manner, and all other users and groups will not see it at all. In short, the file will be removed from all activity but not removed from the Vault.
Once you determine that the file in question has no parents, click Change State and choose Obsolete. This is a good time to exercise the option to add Vault comments. Be descriptive, its the only chance you have before clicking OK.
Bottom line, say it with me: “Don’t Delete, use Obsolete” (that rhymes). Enjoy!
-Brian Schanen
