New Idea
3 Kudos

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;

 

  1. 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".
  2. If you would like to see this workflow be officially supported, please add your comments to this post.

Ryan

 

15 Kudos

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.

11 Kudos

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?

86 Kudos

When creating and working with lifecycle states, I want to be an environment like this...

PLM-LCeditor.png

 

Something with boxes and arrows that I can drag around.  I graphical approach like this is easier to work with and provide an easy way to see how files get routed through the entire lifecycle.

 

75 Kudos
jeff.noel

Rollback Revision Increment

Status: Future Consideration
by Valued Contributor jeff.noel on ‎07-25-2012 12:44 PM

Hi,

 

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.

 

Thanks, 

24 Kudos

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.

 

6 Kudos

Enforce consistent Project file for all clients is a great new option in vault, so that clients use the same vault project file.

 

Please make this an option, to also check that the clients are using the same inventor Project.ipj as the vault.

-We are using a single projetct with Vault 2014. At present, It changes on the clients to Default.ipj every 2nd or 3rd day.

 

best regards

Peter

Status: Future Consideration
We currently have the option to force the Vault project file for Inventor in the Vault settings, however Vault cannot have control of Inventor and what it does outside of Vault, especially if it isn't logged into Vault at the time it starts.
51 Kudos
mthomas

Don't Let the Job Processor Consume an Inventor License

Status: Future Consideration
by *Expert Elite* on ‎06-21-2012 05:45 AM - last edited on ‎07-05-2012 11:25 AM by Board Manager 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

48 Kudos
jbj

Recycle bin

Status: Future Consideration
by Active Contributor jbj on ‎07-17-2012 12:35 AM

Instead of permanently deleting files from vault, make a recycle bin type functionality in Vault.

 

Upon right clicking a folder, we should have the option to undelete the files (with dependents).

 

Emptying the recycle bin should be an administrative task

18 Kudos

My company would like to move to a paperless manufacturing system.

I know that many companies would like to move in this direction and probably have, by using "Workarounds".

I would like the ability to use the following workflow:

 

1.) Create design using Inventor (Creates .idw).

2.) Check the file into Vault (Creates .dwf).

3.) Shop floor opens .dwf (Using Vault & Design Review).

4.) Shop floor creates Redlines and saves file.

5.) Redline file is "Automatically" saved in Vault.

6.) Designer recieves message "New redline available".

7.) Designer checks out .idw and adds redlines as revisions to the .ipt and the .idw and checks file back into Vault.

8.) Vault creates new .dwf of revised file, while archiving the redlined files.

 

Can this be done? This would be a perfect integration.

 

Len

You are not logged in.

Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register

Announcements
IdeaStation Guidelines
Review guidelines and best practices
before posting a new idea
Top Kudoed Authors
User Kudos Count
18
18
13
11
10