New Idea
2 Kudos

The system should have a setting that disables the system ACL security (lifecycle) being applied to the Files on State change or the Folder ACL security should be able to be set to override the State security.

At present I believe that the only way to achieve this is to manually deselect the Security Override option on the File details security tab:


     acl security.png                 

The Application should provide this  option in the administration settings

i.e. if configured automatically resets the file to its original object based security after any state change.

No need to Combine ACL Security, just need a simple on / off to the system security overiding the folder security.

Please Please Please........... 

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.



7 Kudos

I've known this issue has existed from about day one in Productstream and now Vault Pro, but
it's time that this security issue is fixed. I feel its a major defect, but they tell me it's "AS DESIGNED".


If you are using items, this has the potential to be costly to your organization. It allows users to print an older version of a file which has been revised and it still shows the water mark of "RELEASED". All without any kind of warning.


We are dealing with items and when an item has several revisions and you toggle back thru the revisions, the drawings
linked to that revision still have a water mark of released, even though the drawing is an old - revised drawing.


The attached video illustrates this disaster waiting to happen.


There has to be a way to prevent the printing of older drawings with "RELEASED" on them. The water mark should say "VOIDED Drawing" or the like when a user toggles the revision level back. Any guidance here on how to
fix this issue?


Steve Hilvers

4 Kudos

Link numbering schene to categories

Status: New Idea
by gabriele.bonacini on ‎05-12-2014 06:00 AM

At the moment we can link at the categories only lifecicles, properties and revision scheme.

I think it may be usefull to select also the numbering scheme.



2 Kudos

The Vault search text box displays "Search Projects" or "Search Vault Explorer ($)" - often when clicking in the search text box the default text is not cleared and what ever is typed is added to the default text.  The result is that the search is not done correctly.


This behaviour is shown in the attached screen shot.


According to Autodesk Customer Support this behaviour has existed for several releases of the Vault.


I would like the search box default text to clear when clicking in the box to enter data.

86 Kudos

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



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.


76 Kudos

Rollback Revision Increment

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



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.



21 Kudos

Make Synchronize Properties Built in

Status: Solution Provided
by *Expert Elite* on ‎09-13-2013 11:30 AM

I think it is crazy that everytime the state is changed within vault, specifically from "Released" to WIP, I have to synchronize the properties.  Why aren't the properties automatically syncing when the state is changed.  They should be.  Changing states should not be a two step process.

3 Kudos

Vault Feature Request: When you obsolete an item it should obsolete all previous revisions, released or not.


Obsolete Items are still viewable in Web Client because some previous revisions are released


Ref: previous Autodesk case 09411810 and new Autodesk case 09515277


Also see attached Word doc with relevant context as "Obsolete Item scenario - public.doc"


The customer has the advised workflow and has asked for this feature request case be opened with Autodesk to obsolete all previous revisions, released or not.


The reasoning is so that Web Client users cannot access parts in error that are no longer in production.


The business case for this company involves 35 seats of Vault Pro 2014 and several dozen more Vault Web Client users at multiple sites routinely relying upon the accuracy of parts that are accessible as 'in production'.


They do not want obsolete parts being requisitioned or ordered as parts of extensive bills of material, for example.


They understand that this feature request will likely not be made available in Vault 2014. They have the workflow workaround in place as an alternative as detailed in the attached Obsolete Item scenario - public.doc

44 Kudos

Better tools for managing security

Status: Accepted
by Employee Redmond.D on ‎06-26-2012 05:11 AM

Folder and lifecycle state security is a useful feature, but it can be really hard to use.  For example, it's hard to find out which users have access to which folders.  Likewise if a user doesn't have access, it can be hard to figure out why.  If you are managing many folders, you are forced to manage them one at a time.


One possible improvement to provide a view like in the Effective Folder Permissions app, which unrolls the security settings to show a per-user view.


Status: Accepted

You are not logged in.

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

IdeaStation Guidelines
Review guidelines and best practices
before posting a new idea
Top Kudoed Authors
User Kudos Count