powerJobs Processor v22
v22.0.22
01-02-2022
Fixed
Issue where the Job Processor produces notable overhead for each registered custom job on startup when activated via serial number
404 error page “This page does not exist yet” opens after clicking Help → Online Help button in powerJobs Processor window
v22.0.20
16-12-2021
General
Assembly powerJobs.Common gets installed in the GAC
Fixed
Issue with jobs which use custom Applications but fail to load file or assembly ‘powerJobs.Common, Version=22.0….’ after installing updates on Job Processor environment
Issue with failing Open-Document cmdlet which incorrectly reports ‘not supported file type’ when custom Application is implemented and
ApplicationBase.SupportedFileTypes
does not return file extensions in lower case
Breaking Changes
Custom Applications
Replace powerJobs.Common reference in Visual Studio Project: When rebuilding the Visual Studio project the build fails because the assembly powerJobs.Common.dll is not any more available in the directory “C:\Program Files\coolOrange\Modules\powerJobs”. The reference must be removed and the assembly must be re-referenced from the GAC. From now on the custom Application can also be used after updates, without having to rebuild the project with the same assembly version which is installed on the Job Processor environment.
Remove coolOrange.GenerateEngine reference in Visual Studio Project and change namespace:
The reference to the assembly coolorange.GenerateEngine must be removed in your Visual Studio project.
All the required interfaces and abstractions for implementing custom Applications were moved to the powerJobs.Common.dll.
Usages of the namespace coolOranage.GenerateEngine
must therefore be replaced with powerJobs.Common.Applications
.
v22.0.19
06-12-2021
Features
The powerJobs Settings Dialog displays settings based on their type:
Switch settings with yes/no (boolean) values are displayed as checkboxes and can therefore be easily modified
Text settings can be displayed and modified without worrying about correct PowerShell syntax (quotation, escaping etc.)
experienced users which specify more flexibile Powershell settings, those expressions are highlighted in italic and underlined
The jobs working directory (located in C:\Temp\powerJobs Processor...) gets automatically cleaned up after every job execution.
Usages of the Clean-Up cmdlet in custom job scripts are therefore no longer necessary and can be removed.
General
Several modifications to facilitate the usage of Sample Jobs:
Replaced $…FileName settings with easier configurable switches for controlling the name of exported files:
$…FileNameWithExtension settings allow to remove the Vault main file’s extension
$…FileNameWithRevision and $…FileNameRevisionSeparator settings allow to add the Vault source file’s revision label
Removed $local…fileLocation settings which were available in some job scripts
Removed $hide…inVault settings whereby exported files continue to be displayed in the Vault Client
Replaced $fastOpen settings in several jobs with easier configurable $openReleasedDrawingsFast switch
Replaced $workingDirectory settings with global $workingDirectory variable which gets automatically provided for each processed job
v22.0.16
24-11-2021
Features
Extended powerJobs Settings Dialog to allow editing of setting values
General
Jobs directory Windows Permissions changed to Read & Write for Everyone to allow changes to job settings
v22.0.13
16-11-2021
Features
The Submit Job button allows to queue jobs not only for selected Vault Files but even for Folders, Items, Change Orders and Custom Objects (removed -FileId parameter) : - The jobs are queued for the specific version of the selected Vault entity
v22.0.12
11-11-2021
Features
New powerJobs Settings Dialog to display Job Scripts and their Settings
Introduced Settings region to expose configuration options of jobs
General
Sample Jobs have been extended with Settings regions
-
The Create PDF button and the powerJobs → Job Dialog menu entires have been removed from the Vault Client
Vault Administrators can instead start the powerJobs Settings Dialog via Tools → powerJobs Settings…
The Submit Job button only allows installed powerJobs Jobs to be queued and only for a single selected Vault File
The Job Queue gets automatically enabled once the powerJobs Settings Dialog is opened and no longer during the Vault Log-in
Fixed
Export-Document and Sample Jobs:
Issue with failing exports of sheetmetal parts to DXF and DWG on Windows locales with decimal separators other than ‘.’ (dot)
Issue with corrupted PDF files exported from Inventor drawings, when invalid values were specified for the option
Vector_Resolution
v22.0.8
25-10-2021
Features
Vault Administrators are informed to start Inventor on newly set up Job Processor environments
General
Improved error messages of Cmdlet Open-Document when Applications can not be started (e.g. because of license issues with Inventor, unexpected instabilities with InventorServer or DWG TrueView)
Updated Licensing to version: 18.2.27
Fixed
Issue that Assert Failure dialogues prevented the user from starting the powerJobs Processor on environments where the product or the corresponding License Information Tool have never been started before
Issue with hanging jobs which are blocked by the Open-Document Cmdlet and an opened Registration of Inventor.exe dialog on environments were Inventor was never stared before
v22.0.7
30-09-2021
Features
New sample Job Sample.CreateDXF&STEPfromSheetmetal for creating DXF and STEP files from sheet metal parts with simple configurable settings
Extended sample Jobs Sample.CreatePDF, Sample.CreateDXFfromDrawing and Sample.CreateSTEPfromModel with simple configurable settings like publishing the file to a dedicated network-share
General
Renamed Sample Job Sample.CreateDXF to Sample.CreateDXFfromDrawing
Renamed Sample Job Sample.CreateSTEP to Sample.CreateSTEPfromModel
Updated Licensing to version: 18.2.26
v22.0.3
19-05-2021
Features
powerJobs Processor automatically logs into Vault with the saved Job Processor login credentials
Fixed
Issue with user names which contain white spaces could not be used with powerJobs Processor for logging into Vault
Issue that Assert Failure dialogues prevented the user from starting the powerJobs Processor on environments were no Job Processor login credentials has been saved previously (or after installing Vault Client updates)
Issue with starting the powerJobs Processor when authenticating using Autodesk ID (Vault 2022)
Issue where cryptic error messages were displayed when problems has been detected during the start of powerJobs Processor
v22.0.1
29-04-2021
Features
Added support for Vault, Inventor and DWG TrueView 2022
General
Updated Licensing to version: 18.1.24
End User License Agreement (EULA) has changed
Removed DEPRECATED support for removed Add-Log cmdlet in 19.0.7
Removed DEPRECATED support for removed ErrorMessage property on results of document related cmdlets in 19.0.7
Added DEPRECATED support for replaced $changeOrder
Fixed
Issue that error messages displayed <No File> instead of <ScriptBlock> in the stacktrace when an error occurred in a script block.
Breaking Changes
Replaced $changeOrder
The $changeOrder object of type Autodesk.DataManagement.Client.Framework.Vault.Currency.Entities.ChangeOrder provided in Jobs has been replaced by the powerVault ChangeOrder object.
Members of $changeOrder used in Scripts such as EntityIterationId
and Number
should therefore be replaced with Id
and _Number
.