At my point, it miss the ability to go from the software file directly to the same file in the vault explorer.

It would be perfect to be able to right click in the navigator/explorator of the software where we are working right now to directly have the vault explorer open and the same file selected. Or, at least, visible.

You can actually open a file from vault but not the other way.

Regards 

Francis

Description

Starting a folder structure for a new project in Vault can be a timely process. From reproducing the folder structure, and in particular having to manually assign permissions to the newly created project structure.

Impact

Not having this feature has a significant impact on the process for starting a new project, particularly one which has a somewhat complex folder structure.

Due to this product limitation, it might actually put users/clients off from using Vault in the first place if there is such a time consuming project startup administration process.

Severity

Medium-High

Solution

Roll the Autodesk Vault 'Clone Structure' Add-in from Autodesk Consulting in as a permanent feature in Vault to aid in speeding up the project startup process.

http://underthehood-autodesk.typepad.com/blog/2011/09/meet-the-new-project-same-as-the-old-project.h...

I'm not sure if it is allowed to request new API features in Idea Exchange.

It should be possible to enable/disable custom commands introduced by a vault extension. E.g. if a command is only available for a special user (Administrator) the command should be disabled for all other users.

--Stephan

Storing data in system options is restricted to administrators. Why? Propably something like user options writeable for all users would be a solution.

We are developing vault explorer extensions and we often have to store data which must be available / writeable for all users.

--Stephan

I realize this may be a little backwards and may be more of an Inventor feature, but I would love to see better compatability between iLogic and Vault.

For example:

We are currently in the process of automating our engineering process, and that includes iLogic models. But in order to check them into Vault, after we have re-configured a model, we will have to go through some extra steps to check it back into Vault.

Our plan is to keep our iLogic model in a seperate folder in our folder structure. All parts in the iLogic models will have generic part names. When the model is re-configured we will have a "Finalize" rule. Before the Finalize rule can run, we will need to get all of the folders that have the actual parts into our Workspace. Then we can run the finalize rule wich will check to see if the new part numbers exist in the current folders. If they do exist nothing happens, if the file is not found, it will do a "Save As" for that part into the correct folder. Once all of the parts in the assembly have been checked, it will then do a component replace for every part in the assembly with the actual production parts from the appropriate folders in our file structure. Finally it will do one more "Save As" and save the main assembly into the correct folder. Now we will be able to check that file into Vault. All new parts will be check in and any parts that already existed, will not have been changed so there will be no conflict. Once this is all done, we can then go back and delete all of those files out of our Workspace.

I would love to have a way to do this without having to run through the extra steps, that I have outlined here.

If someone knows a better way, I would appreciate any insight you may have.

Thanks,

Chad

I would like to be able to compare DWFs directly in Vault of released drawings. It would be faster than "getting" the dwfs local to compare in DR. It would be great if this could be extended to the web client as well.

This used to be a function available in ADMS 4.5 but went away for some reason. It would be great to see it come back.