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.
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 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."
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.
When exporting the BoM table from Vault Pro, there is no way of showing the BoM level indicator (which it does in Inventor). This is really annoying as the whole purpose of exporting the BoM is to then import into another system, such as SAP or perhaps a Spreadsheet. Without the BoM level indicator this is really difficult (actually impossible).
The other way is to use the Export Items tool (right click in the BoM tab), however all the Items must be set to ‘released’ for this to work. Sometimes I want to export for progress reporting, and all the Items are not yet released. Please add an option which allows us to export the Items at any Lifecycle stage. Currently the Software is far too restrictive for users in the real world.
Maybe in Vault Pro or Colaboration this is a function, but in workgroup the ability to roll back to a previous revision is not there. I have had this function in other PDM softwares. This needs to be considered strongly as a much needed enhancement.
I would like to have controls over the types of files that the Job Processor creates visualisation files for (DWF's).
I use the CC for about 50% of the parts in an assy and I have the visualisation files created on Lifecycle change to Released. I don't need visualisation files (DWF) to be generated for Bolted Connections, placed Content Centre files (standard or custom), Frame Generator files and such. I have no need to see DWF's of these or to supply them to another user. And the assy DWF file doesn't need the child DWF's either. It's just clogging up an already taxed Job Processor machine.
We have a company numbering scheme to mirror into Vault. The numbering scheme has been historical to our company procedures for many years and we wanted the same scheme used in the Vault. The scheme requires a number of different prefixes to help categorise the Drawings / Documents, then every Drawing / Document has a different Sequential number. However the software only allows a new seq.no if all the prefixes are the same. I would have thought our proposed scheme was a fairly standard way of setting up a numbering scheme. Please rectify for future releases.