Spring cleaning

With the launch of the #21 product release, which will happen next week, we cleaned up the product line and had some rebranding.

The probably world’s best-selling Vault Job Processor add-on, powerJobs has enabled so many customers to automate tasks such as PDF publishing, DXF creation, email notification, printing and more. Its simplicity and flexibility allow you to create any type of job with minimal scripting knowledge. There is a question that new customers ask almost every time: “I have x Vault seats, how many powerJobs do I need?”.  The answer is: “one powerJob per Vault Job Processor!”. We have decided to rename powerJobs to powerJobs Processor to make it easier to associate it with the Vault Job Processor. There is another reason why we did this, namely, to rename jobWatcher to powerJobs Client. powerJobs Client is the perfect companion to powerJobs Processor. It informs the user when a job is in the queue (sensibilization) and, more importantly, it informs the user when his job encounters a problem. This ensures that workflows are not interrupted. Renaming it to powerJobs Client makes it easier to understand that powerJobs Processor and powerJobs Client simply belong together.

Last year, we introduced a new product called vaultFLC that easily connects Vault to Fusion Lifecycle (FLC). It requires little configuration and is ready to use in minutes. This has changed the landscape of how Vault connects to the Fusion Lifecycle. Next week we will release the next generation of the vaultFLC connector, which still retains the same simplicity but uses the flexibility of PowerShell to configure and customize existing workflows and create additional custom workflows. That’s why we’ve decided to rename vaultFLC to powerFLC. powerFLC is consistent with the other powerXXX products, completing the product line to enhance your Vault environment and connect it to the rest of your organization. There will be a powerFLC Processor running on the Vault Job Processor and the powerFLC Client to connect Vault-client-side workflows to Fusion Lifecycle.

This entry was posted in Fusion Lifecycle, powerJobs. Bookmark the permalink.