Job Triggers Tab
The Job Triggers Tab of the powerJobs Processor Settings Dialog displays the Triggers for the selected job and allows to configure them.
The configured Triggers only apply to the current Vault.
Job Triggers do not support replicated environments.
The input masks in the beginning of the Job Triggers tab allow the following configurations:
The description for the queued job. The entity name will be appended automatically. E.g. the description “Publish PDF” results in “Publish PDF: Bosch Caster.idw”.
If no description is set, a default value containing the job’s name will be used.
The priority wherewith the job is queued. The minimum priority value is 1 (highest priority) and the maximum value is 200 (lowest priority).
Filters are conditions that the entity (File, Item, Change Order, Custom Entity) must meet, for a job to be queued when a configured trigger takes effect. Filters are applied on Vault properties (system- and user-defined properties).
When no filters are set, the job is always queued for the entity. When multiple filters are set, all filters must match for the job to be queued.
It is possible to specify one or multiple values for each filter. When multiple values are set, at least one value must match for the filter to match. Multiple values must be separated with semicolons (
Refer to the following example to queue the job only for files with the file extension
dwg, and which are assigned to the Category
Engineering the following filters can be used:
One filter for the
File Extensionvault property with the filter value
idw; dwgto match both extensions.
A second filter for the
Category Namevault property with the value
The previously mentioned settings can be considered as general settings because they apply to all the triggers which can be configured in the tabs beneath:
Lifecycle State Change Trigger to queue the job based on a lifecylce state change in Vault
Context Menu Trigger to display a context menu item in the Vault client to manually queue the job
Trigger job automatically on lifecycle state changes
The tab Lifecycle State Change displays all the available lifecyle states for the selected job’s entity type.
It allows then to configure one- or multiple target states which queue the job, when a jobs entity (File, Item, etc…) reaches the according state and when all configured filters apply.
To disable the Lifecycle State Change trigger no state can be selected.
Lifecycle States are displayed in the format:
Lifecycle Name / State Name and for Change Orders:
Workflow Name / State Name.
Requires powerJobs Client
This feature requires powerJobs Client (version 23.0.1 or newer) to be installed on the workstations as it relies on the SubmitJobsOnLifecycleTransition script.