Automate and delegate repetitive tasks to the Vault Jobprocessor
Enhance your Vault workflows with custom actions and checks.
When it comes to automate and delegate work to a dedicated machine, powerJobs is THE Vault Jobprocessor extension you need.powerJobs »
You are using the Vault Job Processor? Stay informed when jobs are running into problems and keep your work flowing.jobWatcher »
Do you like to enhance your Vault workflows? Then powerEvents will let you consume all the power of Vault in a simple way.powerEvents »
powerJobs makes it possible to create custom jobs via a simple scripting language. No need for high end development skills. It comes with ready to use samples for the most common use cases, such as publishing to other file formats, sending email notification and printing.
Just release your CAD models and let powerJobs create a PDF, DXF, DWG and other format for you. Have those files stored inside Vault, on a network share, FTP, Cloud, or any other location.
You have particular requirements, like watermark, publishing just specific views or layers, and the like? No problem, just tweak the script the way you like.
Inform your purchase department, or other people in your organization that a new version of a drawing, item or bill of material have been released.
Have powerJobs send emails to your peers, on given Vault actions, with custom content, automatically.
Print all the drawings of an assembly or bill of material, in the right format, to the right printer, at the right department.
If printing paper is still your thing, then don't spend valuable time in doing it manually. Have powerJobs printing the drawings for you, on the server, so that you can carry on with your important work.
As we designed powerJobs more than 6 years ago, we always had in mind all the possible different customer situations. Therefore we decided not to limit powerJobs to the settings of configuration file, but instead we looked for a simple and widely used scripting language.
Windows PowerShell was our choice, as it's widely used by IT people, it simple and yet powerful, and it's a Microsoft language, and therefore supported by all Microsoft operating systems. The result surprised also our self.
With powerJobs, you get a list of preconfigured, working, sample jobs, which can be used as they are, or can be tweaked and extended. On our wiki page and our support portal, you'll find the complete documentation, as well as tutorials, code snippets, and more. Also, you are welcome to use our support-forum, where we can help you make the best use of powerJobs.
Would like to add more control to lifecycle transitions? Or perform an action on certain check-in/-out operation, or other Vault actions? Vault permits to be customized for several years, but this was limited to developers only. powerEvents makes it now easy to add custom logic via the Windows PowerShell scripting language, so that you can tweak your Vault the way you want.
Vault gives you several settings to be configured in the admin panel, in order to control who can move the file, item, change order, to a give state. However, you can't go beyond those settings. With powerEvents you can.
You can check the value of a property, and so preventing releasing a file, when some properties contains words like "test" or the like.
You can apply advanced checks, and so implement a 4-eye release mechanism, so that must be checked by two different persons.
In combination with powerGate, you can check whether the part number is valid within your ERP system and so prevent releasing files with wrong part numbers.
Did you know that Vault can execute custom actions on lifecycle transitions, check-in/-out, and other events? powerEvents makes this accessible to everyone via scripting.
powerEvents can help you queueing jobs in a better way, by queueing the right job for the right file, item or change order, with the right priority, and a meaningful description.
It can also automate working steps, like creating links between files, items and change orders, or moving or renaming them, or any other Vault action.
In combination with powerGate, it may sync the state of items between Vault and your ERP, or other similar actions.
powerEvents joined just in 2016 the product line, and captured the hearts of many customers right away, as it finally empowered them to bring their Vault to the next level.
The simplicity of the Windows PowerShell, makes it possible to subscribe the available Vault events and either control the execution of such, or perform actions before or after the events gets fired.
With powerEvents, you finally can enhance the Vault workflows the way you like and bring more control and action into your daily work. On our wiki page and our support portal, you'll find the complete documentation, as well as tutorials, code snippets, and more. Also, you are welcome to use our support-forum, where we can help you make the best use of powerEvents.
Delegating repeatable tasks to the Job Processor is a great thing. As these tasks are part of your workflow, it would be good to make Vault users aware that there are jobs, triggered by them, running in the background, and inform them in case of troubles. Being informed when a job fails, helps addressing the issue right away, reducing so the risks, delays and costs of an interrupted workflow.
When changing state of files or items, jobs may be queued. These jobs have important tasks, such as creating PDF, updating properties, title-blocks, revision table, translating into other formats, informing people via email and the like. Users do usually not care, and that is fine, but it’s good to remind them that once they are done, the Job Processor may still have some work to do.
jobWatcher will inform the users about his jobs, in a non-intrusive way, by using the Windows 10 notifications. In case where one or more jobs are queued, a notification will pop up and then fly away. Multiple jobs will be summarized to a single notification, so that users will not be distracted too much.
jobWatcher informs about all types of jobs, both the Vault standard and custom jobs. It also does not matter how the jobs are queued, thus also jobs queued by powerEvents or other tools will be noticed.
In case a job triggered by a given user will quit with a failure, then jobWatcher will inform that users about the problem, so that he can take care. Doing so, the process which triggered the job can be fixed and completed in a timely manner. The user usually knows the context which triggered the job and knows the files involved in the job, so that error handling can be done faster and better.
The error notification sent by the jobWatcher will be sticky. So, even if the user is not at his desk at the moment of the problem, the message is stored inside the Windows notification center.