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).

I've suggested this on the 2014 beta forums, and have been advised to post it here.

A lot of end users don’t even know the JP exists, the ones that do will sit there waiting for it to do it’s thing but there’s no obvious indication that the JP is even processing their job (yes there is the Job Queue but I’ll get to that).  Could you please consider implementing some sort of graphic visual, whether that be a property, field, column, whatever, but something to show a user that the JP is actually processing a job for the file(s) they’re looking at.  I appreciate that as with anything, the technicalities of this will be tricky, but it would be very useful to have.  As an administrator I can RDP onto the JP box and pause/resume the JP and witness what it’s doing, a user cannot, they won’t know if their job is 15 minutes away from being done, 5 minutes, if the JP has bombed out, and I don’t want them to rely on the job queue either as this is often full of errors and a typical end user won’t be able to make any sense of that job queue. 

You can only select roles which has certain permissions, but you cannot assign a certain permission to a role.

It may be more flexible if you can create new roles and add permissions, or modify existing role permissions with UI (something like a spreadsheet format and able to change settings by clicking)

It would REALLLY save us a lot of time when dealing with old or contractor files if this limitation could be removed. See attached picture. If you can do this manually I dont see why it cant be done via a search select all and drag to new folder. This would save us many many hours.

Forum Post: WISH - Copy files from multiple folders into one folder

Please change the Auto Numbering tool so it checks the database for unused/used numbers instead of just taking the next number in the list based on the last number assigned.  Even if the number hasn't been used (i.e: make components command is cancelled) the number is taken and can't be used again. This can cause problems in companies which use numbering systems based on specific situational criteria. Contact me for more information.

I like to use boolean expressions in searches.

For example:

(file name = "bracket") OR ( (file name = "lifting eye) AND (state = 'released") )

This would give me all brackets and all lifting eyes which are released

Currently there is no method to assign the revision scheme duing item creation, including when assigning items to files.

We use two revision schemes... our default is numeric based starting at 0. We use "0" as the released to production revision. Our proposal scheme uses letters and starts at A. The way it is now I create a new item, which is assigned a revision of 0. I save the item and then adjust it to A. This consumes the 0 which cannot be used again. What I'd like to see is the option to select the revision scheme while both creating the item from the item master AND duing item assignment when assigning items to files

Can you add the possibility to choose how Vault Explorer will open file, when double-click? Because actually, when double-click an assembly file (IAM) in Vault Explorer (Workgroup or +), it will always open this files with option release-biased. But many people want to double-click on this assembly an open the none-release-biased assembly. Actually, the only method is to use the Open-from-Vault command in Inventor Vault-addin. Thanks in advance.

Currently, so I am told, there is no integration between Item properties and those in File Store on the same object.

Example:  A file in File Store is at Revision 0, you assign it to an Item in the Item Master.  In Item Master change the revision (manually or through an ECO or Lifecycle change), and push that revision out to the CAD file (idw or ipt etc).  Make changes to the CAD file, save and check back in to Vault.  The file in File Store is still at Rev 0, though the ITEM is at Rev 1.

Linked with this, the Vault Revision Table.... pulls it's Revision value from the File Store value... so if it's not in sync with Item Master... it becomes a useless tool.