Tag: job processor

  • BOM Report Job

    To celebrate the release of Vault 2015 R2, I wrote an app that lets you generate BOM reports automatically through the Vault job server. If you are not already aware, Vault 2015 R2 has a BOM Report feature. From any BOM view, you can run the Report command and it will generate a report of…

  • Job Processor Updates in 2014

    In an effort to address some long standing Job Processor issues, some major changes were made in 2014. At the time of this writing, there are still some issues being worked on, so be sure to read the workarounds at the bottom of the post. But let’s start with the good news.

  • Job Processor logins

    Job Processor is constantly logging in and out of Vault. So plugging-in to that app is different that with Vault Explorer, where you assume that the user is mostly staying logged in as a single user. Job Processor, on the other hand, may have zero, one or two simultaneous log-ins at any given time.

  • Custom Jobs without Job Processor

    If you are building your own custom job, you do not have to plug-in to Job Processor if you don’t want to. The job queue can be accessed through the Vault web services API, just like with files and folders. The recommended approach is to use Job Processor. That approach is what you see in…

  • More on Hacking

    I indicated very clearly that my last post was a hack. I want to take a bit of time to explain exactly why it was a hack. I’ll also point out things that were not a hack.

  • My Fake Job Processor

    This article is such a hack that I created a new category to mark the occasion. It goes without saying (but I’m going to say it anyway) that Autodesk isn’t going to provide support for what I’m about to say. In talking with people about various Vault customizations, I find that sometimes it would be…

  • Job Processor Command Line Tricks

    We are working on multiple fronts to address many of the Job Processor issues that people are running into. For this post, I want to point out some command line features we added to Vault 2013. This feature won’t fix all problems, but it has many uses.

  • Q-Tools and Watch Folder 2013

    For this post, I bring you two whole apps. I’ve updated Q-Tools and Watch Folder for Vault 2013. Technically the 2012 versions can still work with Vault 2013 server, but there were a few optimizations I wanted to do using the new API features.

  • Lifecycle Event Job Parameters

    When jobs are created from a lifecycle state change, the job will have a specific set of parameters depending on the entity type. Here is the list of parameters.

  • Job Queue Priority

    Some people have noticed that there is a new job queue column called Priority. This is an API feature, at least for now. So you have to use custom programming if you want to make use of this value. From Vault Explorer, you can see the value, but you can’t do anything with it.