When using Windows Authentication, the username used by Vault to fill checkin by, check-out by etc. is the DomainName\UserName. Can you add an option to use the initials or the Display Name of the Windows user. Or add a way to create in Vault a display name for promoted users.
I would like to see an option to reset the rev scheme to the same value as a brand new file, and to reset the revision history of that file on Copy Design.
Because of legacy data from Vault Basic with manually managed rev values, I have 2 different rev schemes and 2 properties to synchronise. 1 scheme for pre-manufacture (A, B, C, etc...) and 1 for released for manufacture (1, 2, 3, etc...). I have a situation where I have a released file at rev 2 that I copy design. As an example the IPT file changes to rev 1 but and the IDW file changes to A. I have a process that sometimes works to reset the rev and history. I change category of these 2 files to Base, then revise them to Null rev scheme, then change category to Engineering (default for Inventor files) which creates the rev value A. If I then work on that file and try to release it to the manufacture rev scheme (1, 2, 3, etc...) I can't get it to work properly. The IDW file will change to 1 but the IPT file changes to 2. And the previous rev history remains so when I place a rev block it contains all of the previous data.
I've come to the conclusion that it is often easier to just start with fresh files and re-model.
Give the Vault administrator the ability to set fixed priority values for specific job types. For example, DWF generate jobs could be set to always have a priority of 100, regardless of how they got added to the job queue.
the goal is to run the job processor on many files that are spread accross several replicated servers.
the hurdle is that if you have the job processor logged into one server and it attempts to process a file that is currently owned by a different server, the task cannot be completed successfully. "error"...
we need to be able to allow for this in the job processor settings, whether it is to simply choose
1. "skip file that is not owned by your server", or
2. "run jobs on tasks with preference to one server over another". the job processor would be able to batch together a few hundred jobs for example, to complete on the local replicated server, then reboot itself (or log out and log into a different server) to run a few hundred files that are owned by the other server(s).
3. allow the job processor to run on files regardless of whether they are owned by another server, or
4. allow the option to choose: "if files are owned by a different server, then just run (several topions may be available here).
there may be easier ways to manage this but the job processor is going to be of much more use with some enhancement. (to be read in consideration with the several other requests for job processor improvements currently on the ideas station and discussion forumns).
on 07-12-201204:35 AM - last edited on 07-12-201204:37 AM |
When an ECO is generated, a work list item is created for those on the ECO routing. I would like to be able to link this to, or use it to create, an MS Outlook task. Either that or tweak the work list items so they behave like a task in Outlook. It would be nice to have the ability to set the state of the task, the percentage complete... and also use reminders and alerts for the due dates. Right now a work list item just.... sits there... looking pretty.