powerEvents v22
v22.0.5
02-03-2022
Features
New client customization SubmitJobsOnLifecycleTransition.ps1 to submit jobs on lifecycle transitions configured in the powerJobs Settings Dialog.
Configuration for Vault UDP to submit the Sample.CreateDXF&STEPfromSheetmetal job only for Sheet Metal parts is no longer required and is now determined by the script.
Technical Preview: Client customizations (scripts and modules() can be easily distributed and will be automatically downloaded to all workstations upon application startup
General
Updated Licensing to version: 18.2.27
Removed Sample.SubmitPublishingJobsOnRelease.ps1 sample as the functionality is replaced by SubmitJobsOnLifecycleTransition.ps1
Directory of Client Customizations: Windows Permissions changed to Read, Write & Delete for Everyone to allow synchronizing scripts and modules
Removed support for Custom Objects in the Sample.ValidateProperties.ps1 script as it was not working properly.
Fixed
Fixed and issue in the Sample.ValidateProperties.ps1 script which caused it to mistakenly show a restriction when the vault displayname differed from the account name for the same user.
v22.0.4
08-10-2021
Features
New client customization script Sample.SubmitPublishingJobsOnRelease replaces the script Sample.TriggerDwfJobOnRelease and handles the publishing of PDF files on the release of Inventor and AutoCAD drawings, and of DXF and STEP files after releasing sheet metal parts.
Simple configurable settings allow further customization.New client customization script Sample.RestrictDisturbingSubmittedJobs.ps1 to restrict changing the Lifecycle state of files as long as not all their jobs have been processed successfully
General
Updated Licensing to version: 18.2.26
v22.0.1
28-04-2021
Features
Added support for Vault 2022
General
Updated Licensing to version: 18.1.24
End User License Agreement (EULA) has changed
Breaking Changes
Linked properties of Items passed in the ChangeOrder events have a prefix
Linked properties of ChangeOrder Items have to be retrieved by using the ‘Record_’ prefix within the AddChangeOrder and CommitChangeOrder event actions.