# powerJobs Processor v22

## v22.0.22

`01-02-2022`

**Fixed**

- Issue where the [](</jobprocessor>) produces notable overhead for each [registered](<jobprocessor:job synchronization>) custom job on startup when activated via [serial number](<activation_and_trial_limitations:stand alone licensing>)
- 404 error page *"This page does not exist yet"* opens after clicking **Help → Online Help** button in [powerJobs Processor](<jobprocessor:extended jobprocessor ui>) window

## v22.0.20

`16-12-2021`

**General**

- Assembly _powerJobs.Common_ gets installed in the GAC

**Fixed**

- Issue with jobs which use [custom Applications](<jobprocessor/applications:custom applications>) but fail to load file or assembly *'powerJobs.Common, Version=22.0....'* after installing [updates](<installation:updates>) on Job Processor environment
- Issue with failing [](</jobprocessor/code_reference/cmdlets/open-document>) cmdlet which incorrectly reports '*not supported file type*' when [custom Application](<jobprocessor/applications:custom applications>) is implemented and {code}`ApplicationBase.SupportedFileTypes` does not return file extensions in lower case

:::{dropdown} Breaking Changes
	:title: bg-warning
  **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](<jobprocessor/applications:Visual Studio Project setup for Custom Applications>).
  From now on the [custom Application](<jobprocessor/applications:Custom Applications>) can also be used after [updates](<installation: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](<jobprocessor/applications: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](<job_configuration: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](</jobprocessor/jobs/setup_job>) (located in *C:\\Temp\\powerJobs Processor\\...*) gets automatically cleaned up after every job execution.
  - Usages of the [](</jobprocessor/code_reference/cmdlets/clean-up>) cmdlet in custom job scripts are therefore no longer necessary and can be removed.

**General**

- Several modifications to facilitate the usage of [](</jobprocessor/jobs/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](</jobprocessor/jobs/setup_job>) variable which gets automatically provided for each processed job
## v22.0.16

`24-11-2021`

**Features**

- Extended [powerJobs Settings Dialog](<job_configuration:powerjobs settings dialog>) to allow editing of setting values

**General**

- [Jobs directory](<installation:windows permissions>) Windows Permissions changed to **Read** & **Write** for **Everyone** to allow changes to job settings

## v22.0.13

`16-11-2021`

**Features**

- The [Submit Job](<job_configuration:queueing jobs>) 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](<job_configuration:powerjobs settings dialog>) to display [Job Scripts](<jobprocessor/jobs:job scripts>) and their [Settings](<jobprocessor/jobs:job settings>)
- Introduced [Settings](<jobprocessor/jobs:job settings>) region to expose configuration options of jobs

**General**

- [](</jobprocessor/jobs/sample_jobs>) have been extended with [Settings](<jobprocessor/jobs:job settings>) regions
- [](</job_configuration>):
  - 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](<job_configuration:powerjobs settings dialog>) via **Tools → powerJobs Settings...**
    - The [Submit Job](<job_configuration:queueing jobs>) button only allows installed [powerJobs Jobs](<job_configuration:queueing jobs>) to be queued and only for a single selected Vault File
- The Job Queue gets [automatically enabled](<job_configuration:requirements>) once the [powerJobs Settings Dialog](<job_configuration:powerjobs settings dialog>) is opened and no longer during the Vault Log-in

**Fixed**

- [](</jobprocessor/code_reference/cmdlets/export-document>) and [](</jobprocessor/jobs/sample_jobs>):
  - Issue with failing exports of sheetmetal parts to [DXF](<jobprocessor/code_reference/cmdlets/export-document/dxf:Sheet Metal Parts>) and [DWG](<jobprocessor/code_reference/cmdlets/export-document/dwg:Sheet Metal Parts>) on [Windows locales](<https://support.microsoft.com/en-us/office/change-the-windows-regional-settings-to-modify-the-appearance-of-some-data-types-edf41006-f6e2-4360-bc1b-30e9e8a54989>) with decimal separators other than '.' (dot)
    - Issue with corrupted [PDF](<jobprocessor/code_reference/cmdlets/export-document/pdf:Inventor and InventorServer>) 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 [](</jobprocessor/code_reference/cmdlets/open-document>) when [](</jobprocessor/applications>) can not be started (e.g. because of [license issues](<https://knowledge.autodesk.com/support/inventor/troubleshooting/caas/sfdcarticles/sfdcarticles/Inventor-cannot-access-your-license.html>) with Inventor, unexpected instabilities with InventorServer or DWG TrueView)
- Updated Licensing to version: [18.2.27](<licensing:change_logs/license_v18:v18.2.27>)

**Fixed**

- Issue that *Assert Failure* dialogues prevented the user from starting the [powerJobs Processor](<jobprocessor:extended jobprocessor ui>) on environments where the product or the corresponding [License Information Tool](<activation_and_trial_limitations:license information>) have never been started before
- Issue with hanging jobs which are blocked by the [](</jobprocessor/code_reference/cmdlets/open-document>) Cmdlet and an opened [Registration of Inventor.exe](<https://knowledge.autodesk.com/support/inventor/troubleshooting/caas/sfdcarticles/sfdcarticles/Inventor-exe-needs-to-be-re-registered.html>) dialog on environments were Inventor was never stared before

## v22.0.7

`30-09-2021`

**Features**

- New sample Job [Sample.CreateDXF&STEPfromSheetmetal](<jobprocessor/jobs/sample_jobs:sample.createdxf&stepfromsheetmetal>) for creating DXF and STEP files from sheet metal parts with simple configurable settings
- Extended sample Jobs [Sample.CreatePDF](<jobprocessor/jobs/sample_jobs:sample.createpdf>), [Sample.CreateDXFfromDrawing](<jobprocessor/jobs/sample_jobs:sample.createdxffromdrawing>) and [Sample.CreateSTEPfromModel](<jobprocessor/jobs/sample_jobs: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](<licensing:change_logs/license_v18:v18.2.26>)

## v22.0.3

`19-05-2021`

**Features**

- [powerJobs Processor](<jobprocessor:extended jobprocessor ui>) automatically logs into Vault with the saved [Job Processor login credentials](<https://knowledge.autodesk.com/support/vault-products/learn-explore/caas/CloudHelp/cloudhelp/2021/ENU/Vault-Admin/files/GUID-5D7F921E-B5C3-4A89-9BB0-A7271FF4010A-htm.html>)

**Fixed**

- Issue with user names which contain white spaces could not be used with [powerJobs Processor](<jobprocessor:extended jobprocessor ui>) for logging into Vault
- Issue that *Assert Failure* dialogues prevented the user from starting the [powerJobs Processor](<jobprocessor:extended jobprocessor ui>) on environments were no Job Processor login credentials has been saved previously (or after installing Vault Client updates)
- Issue with starting the [powerJobs Processor](<jobprocessor:extended jobprocessor ui>) 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](<jobprocessor:extended jobprocessor ui>)

## v22.0.1

`29-04-2021`

**Features**

- Added support for Vault, Inventor and DWG TrueView 2022

**General**

- Updated Licensing to version: [18.1.24](<licensing:change_logs/license_v18:v18.1.24>)
- End User License Agreement (EULA) has changed
- Removed DEPRECATED support for removed *Add-Log* cmdlet in [19.0.7](<change_logs/powerjobs_v19:v19.0.7>)
- Removed DEPRECATED support for removed *ErrorMessage* property on results of document related [cmdlets](</jobprocessor/code_reference/cmdlets>) in [19.0.7](<change_logs/powerjobs_v19:v19.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.

:::{dropdown} Breaking Changes
  :title: bg-warning
  **Replaced $changeOrder**  
  The [$changeOrder](</jobprocessor/code_reference/objects/changeorder>) object of type *Autodesk.DataManagement.Client.Framework.Vault.Currency.Entities.ChangeOrder* provided in Jobs has been replaced by the [powerVault ChangeOrder](<powervault:code_reference/objects/change_order>) object.  
  Members of $changeOrder used in Scripts such as `EntityIterationId` and `Number` should therefore be replaced with `Id` and `_Number`.
:::