With the new updated Thin(web) client using the magnifying glass I can easily see both the thumbnail preview and the DWF Visualization file. However this window is fixed in size and too small making it difficult to properly view the DWF file. I know I can right-click and "Open with DWF Application" but I shouldn't have to.
This window should be changed to that... .
I can resize the Window (and it remembers my size)
have this window open much larger
provide a maximize button that makes the window full screen
When using the Change Order process, the document Properties are not mapped to the Change Order Process (ie. Checker, Approver, Date approved, ECN number into Rev Box on Drawing etc) and so do not refresh during document sign off process. This means lots of manual input required by the Users which is open to mistakes. The whole point of a software driven system it to reduce mistakes by doing the manual input for you. Please rectify Autodesk!
Also on a similar theme, why can’t the change order process automatically change the Lifecycle state of the file (i.e Work In Progress, In Review, Released etc). Again, too much manual input required.
In the Edit Routing window, please add columns for user first name and last name in both the "Change Order participants" grid and the "Routing participants" grid. We import domain users and the user name is not a person's actual name. (see attached image). This does not make for an intuitive interface for the users. Please make the window resizable too.
It would be great if we could configure the software to Remove the 'submit and force approval' button and the 'fast track approval' button. Currently looks the same as the 'submit' button and this will get accidently pressed. I know you are going to say ‘your engineers shouldn’t have permission to force approval’. That’s right, we could set it up so this is the case. Unfortunately, we have had to make all our Engineers Change Order Administrators so they can edit the Change Routing List (Checker etc). Something Autodesk could rectify is to make the Change Order roles more configurable.
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.
"I think it would be useful if PS would email users if they have a checked out file in Vault that has been checked out for more than X number of days/weeks etc without any activity (new checkin). I've found some people purposely or accidentally checkout a file and forget about it. I tried having them create a saved search, but it needs to be more of a "in the face" reminder.
It could also be a popup when you login that says something like... "you have X number of files that have been checked out for X number of days, would you like to checkin the files now?" Granted this may be tougher since you will have to use Inventor to do the actual checkin."
I would like Vault to manage external iLogic rules that are called by Inventor ipts/iams/idws.
These rules are programming code that can affect model geometry, iproperties and drawing views. External rules are saved out to a directory visible to the Inventor project file. By placing them in a directory, it is very easy to share them among different Inventor files and users. If an external rule is edited and re-run on the Inventor file, the Inventor file will change.
Users can add the external rules to Vault using the stand-alone client, but the Inventor Vault Add-in does not see the dependency between the external rules and the Inventor file. If another user, possibly at a remote site, downloads the Inventor file from vault, Vault does not know to bring the external rules too. Users must remember to grab the latest copy of the external rule directory.
Vault should track these file dependencies. The rule files should be subject to the same revision and lifecycle control as any other file in Vault. Users should be able to perform all of the typical Vault commands on these files from the Inventor browser.
We need the ability to store all deployable files related to Inventor in the Vault. This includes, but is not limited to, the ability to put the Design Data folder into vault, and enhanced tools to manage Templates, Style and material libraries, and iFeatures within the Vault. Being able to deploy inventor settings XMLs through the project file would be very useful as well.
Basically, we need enterprise level tools to manage inventor configuration.