I would like to see the ability to make a group an ECO Approver. Creating routing lists would be a lot easier if we could have approval groups set up for our departments that need to approve ECO's.
We would like to use "Unanimous Approval" but it can be tough, because an ECO can get held up if someone is out one day, or on vacation. Approval groups could be set up so that as long as someone from the group approves, the ECO can move on. Vault could still record who did the actual approval, but it wouldn't have to be just one specific person.
I've only just come to realize that Autodesk does not officially support editing of files in the Released state. In every vault implementation I've done, I've configured the file lifecycle definition so that the Administrator account has read/modify/delete permissions for the purpose of doing the occassional edit, without the need to transition to another state (e.g. "Quick Change"). In a related note, if a customer is working with item lifecycles in which the item state determines the ability to edit the file ("Apply Item security to related files"), granting the Administrator account read/modify/delete permissions could be used for the same purpose. In discovering that edits to files in the Released state is considered a bad practice, I asked about Job Processor which operates in the exact same manner but supposedly it does background operations that make these released-based edits an acceptable practice.
So, the purpose of me posting here is two-fold;
How many of you have your lifecycle definitions configured in a similar manner (whereby the Administrator account is configured for read/modify/delete for the purpose of editing in Released state)? I am curious if others are making occassional edits to files in this state without the need to transition to "Quick Change".
If you would like to see this workflow be officially supported, please add your comments to this post.
If a user accidently makes a change state of a model from Released to Work In Progress, it will increment the revision, and then leave us with no way to go back to the previous revision. I understand why you would do this, as we shouldn't be going backwards with Revisions, so I don't believe every user should have access to this functionality, but an Administrator should be able to override the Revision if they determined there was a mistake made and we need to go backwards.
When a file is right clicked in the main window, one has the option of clicking "Go to folder" or "Go to working folder". I get this wrong about 50% of the time. Wouldn't "Go to local folder" or "Go to folder in vault" make more sense?
I need to see files that have the Lifecycle State OBSOLETE in Vault Explorer, but I don't want to see them when I'm using Place From Vault command in Inventor. It would be very handy to have a toggle for this in the Place From Vault window.
on 06-21-201205:45 AM - last edited on 07-05-201211:25 AM by ihayesjr
The job processor also pulls an Inventor license when it is processing Inventor files meaning that I can not have it running during business hours. To me there should be a method for it to update DWF files without consuming an Inventor license
We need to be able to rename iparts and iassemblies after they are created. Currently when I try to do this, I get the message like "Operation failed.! XYZ.ipt is a configuration memeber whose name is define by keys within a configuration factory".
We also need the ability to easily fix the iassemblies after the iparts are renamed. Right now it is a nightmare to rebuild the iassemblies after the iparts are rebuilt.