Configuration

The powerJobs Client is primarily used to monitor jobs submitted from Vault Client, Inventor, and AutoCAD, while powerEvents is responsible for loading for loading Client Customizations.
Both products are Vault WebServiceExtensions and can be loaded in any application that uses a VDF Vault connection and the Autodesk.Connectivity.WebServices.dll.

The loading behavior of the add-ins is controlled by the powerJobs Client.config file, which defines in which processes the add-ins should be active.
By default, these are Vault Client, Inventor, and AutoCAD. The configuration can easily be extended to include additional applications such as PowerShell or Visual Studio Code.
The configuration file is located at %LOCALAPPDATA%\coolOrange\powerJobs Client\powerJobs Client.config.

This is the default configuration:

1
2
3
4
5
6
7
8
9
<?xml version="1.0" encoding="utf-8"?>
<Settings>
        <Applications>
                        <Application name="Acad" />
                        <Application name="Inventor" />
                        <Application name="Connectivity.VaultPro" />
                        <Application name="Connectivity.VaultWkg" />
        </Applications>
</Settings>

Note: The application name represents the actual process name.

Changing the default configuration

In case you want to add or remove applications from the scope of powerJobs Client, follow these steps:

  1. Open the folder %LOCALAPPDATA%\coolOrange\powerJobs Client\

  2. If there is no powerJobs Client.config, create it by copying the above default configuration. Otherwise go to step 3.

  3. Edit the file with an editor. We recommend XML editors like the XML Notepad from Microsoft.

  4. Add a new application element with the desired process name of the application or change/remove an existing application element

  5. Restart the according application

Example: Add the PowerShell ISE

If powerJobs Client should be loaded in an IDE like the PowerShell ISE while debugging powerEvents customization scripts or when scripting with powerVault, we have to extend the config file with a new application.
The process name of the PowerShell ISE is powershell_ise and is added as a new entry:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
<?xml version="1.0" encoding="utf-8"?>
<Settings>
        <Applications>
                        <Application name="Acad" />
                        <Application name="Inventor" />
                        <Application name="Connectivity.VaultPro" />
                        <Application name="Connectivity.VaultWkg" />
                        <Application name="powershell_ise" />
        </Applications>
</Settings>

Example: Add Custom Vault VDF Applications

If powerEvents and the client customizations should be loaded in a custom Vault VDF application, the configuration file must be extended to include the new application.
For example, if the customization scripts should run when using the VaultBrowserSample (included in the Vault Client SDK examples), it must be added as a new entry in the configuration file:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
<?xml version="1.0" encoding="utf-8"?>
<Settings>
        <Applications>
                        <Application name="Acad" />
                        <Application name="Inventor" />
                        <Application name="Connectivity.VaultPro" />
                        <Application name="Connectivity.VaultWkg" />
                        <Application name="VDFGridSample" />
        </Applications>
</Settings>