# powerJobs Processor v23

## v23.0.8

`15-03-2023`

**Features**

- Create [DXF out of AutoCAD DWG](<jobprocessor/code_reference/cmdlets/export-document/dxf:Drawings>) files (using [Inventor and InventorServer](<jobprocessor/file_conversion:Supported Format Conversions>))
- Also the sample jobs [](<jobprocessor/jobs/sample_jobs:sample.createdxffromdrawing>) and [](<jobprocessor/jobs/sample_jobs:sample.createdwg>) can be executed for AutoCAD drawings, as these jobs now use InventorServer by default to process all files

**General**

- [](</jobprocessor/code_reference/cmdlets/open-document>) supports opening AutoCAD DWG files also with [Inventor and InventorServer](<jobprocessor/applications:supported applications>) if they are specified in the *-Application* parameter
- Extended [](<jobprocessor/jobs/sample_jobs:sample.createdxffromdrawing>) and [](<jobprocessor/jobs/sample_jobs:sample.createdwg>) with *$useInventorServer* setting, which allows to easily switch back to Inventor in case of problems with the job execution through InventorServer

:::{dropdown} Breaking Changes
  :title: bg-warning
  **Removed function _Test-ApplicationSupportsDocument_**\
  Previously the function `Test-ApplicationSupportsDocument` provided by the [coolOrange.Applications.psm1](<jobprocessor/jobs:coolOrange.applications>) module, allowed checking if a specific [application](<jobprocessor/applications:supported applications>) supports opening a document.\
  Since AutoCAD DWG files where only supported by the _DWG TrueView_ application, the function allowed e.g. to check whether a DWG file is an Inventor DWG or not:

  | Previous                       | Now                   |
  |--------------------------------|-----------------------|
  | `if (Test-ApplicationSupportsDocument -Application 'Inventor' -Document 'C:\Vault\Inventor\Pad Lock.dwg') {` <br> `    Write-Host "This is an Inventor DWG file"` <br>  `}` |    `$file = Get-VaultFile -File 'C:\Vault\Inventor\Pad Lock.dwg'`<br>`if ($file._Provider -eq "Inventor DWG") {` <br> `    Write-Host "This is an Inventor DWG file"` <br>  `}` |
:::

## v23.0.6

`14-02-2023`

**General**

- Updated powerVault to version: [23.0.11](<powervault:change_logs/powervault_v23:v23.0.11>)
- The setup has been extended to provide a dependency key that is required for other product setups that depend on powerJobs Processor

**Fixed**

- Issue where powerVault was listed twice in Programs and Features after upgrading powerVault
- Issue where uninstalling product also uninstalled [powerVault](<powervault:index>), although it was still needed by other products, e.g. [powerEvents](<powerevents:index>).


## v23.0.4

`30-08-2022`

**Fixed**

- Issue in the [powerJobs Settings Dialog] where entries of the "_Job Type_" combobox disappeared when [custom display scaling](https://support.microsoft.com/en-us/windows/view-display-settings-in-windows-37f0e05e-98a9-474c-317a-e85422daa8bb) settings were used


## v23.0.3

`28-07-2022`

**Features**

- New design for [powerJobs Settings Dialog]: Splitted [Job Settings] and [Job Triggers] into separate tabs for easier configuration and simplified user experience
- New functionality in the powerJobs Settings Dialog to configure **[queueing jobs from the Vault context menu](<job_configuration/job_triggers_tab:Trigger job manually by context menu item>)**
  - Extended [default job trigger files](<job_configuration/job_triggers_tab:default values>) with configuration for context menu trigger

**General**

- Updated powerVault to version: [23.0.6](<powervault:change_logs/powervault_v23:v23.0.6>)
- Added DEPRECATED support for removed *powerJobs\Open-VaultConnection* cmdlet

**Fixed**

- Issue in the [powerJobs Settings Dialog] where saving [lifecycle state change trigger](<job_configuration/job_triggers_tab:Trigger job automatically on lifecycle state changes>) configuration failed when all trigger settings where empty
- Compatibility-Issue with module [coolOrange.powerFLC.Workflows.Common.psm1](<powerflc:workflows:coolorange.powerflc.workflows.common.psm1>) of [powerFLC Processor v23.0.1](<powerflc:change_logs/powerflc_v23:v23.0.1>) (and earlier) which prevented *Open-VaultConnection* from reusing the existing Vault connection in job executions

:::{dropdown} Breaking Changes
:title: bg-warning

  **Removed Powershell support for "Job Description" textbox in [powerJobs Settings Dialog](</job_configuration/job_triggers_tab>)**<br>
  To set the name of the job's entity (File, Item etc...) in the job description, it is not necessary anymore to specify the according Powershell expression in the [Job description](</job_configuration/job_triggers_tab>) textbox. The job's entity name will be appended automatically. To achieve the job description "*Publish PDF: Drawing.idw*":

  | Previous                       | Now                   |
  |--------------------------------|-----------------------|
  |    Publish PDF: $($file._Name) |     Publish PDF       |

  **Removed Open-VaultConnection**\
  Removed the `powerJobs\Open-VaultConnection` cmdlet. Instead, the underlying powerVault [](<powervault:code_reference/commandlets/open-vaultconnection>) cmdlet is used directly.

  This means that *unnecessary* additional functionalities for jobs are no longer executed (the "filterconfig.xml" configuration for AutoCAD block attributes is no longer downloaded, local workgroup is no longer recognized in replicated Vault environments, the "JobProcessor.exe.config" file is no longer loaded in PowerShell IDE).
:::

## v23.0.1

`21-04-2022`

**Features**

- Extended [powerJobs Settings Dialog] with new [Job Triggers](<job_configuration/job_triggers_tab:Trigger job automatically on lifecycle state changes>) section which allows to configure **automatic queueing of jobs based on Vault lifecycle state changes**.
  - Providing [default Job Triggers](<job_configuration/job_triggers_tab:default values>) for some jobs. The values are retrieved from newly delivered files (ending with `.defaults`) in the jobs directory.
- Jobs can be [associated to Vault entities](<jobprocessor/jobs:job entity type>) (important for the previously mentioned Job Trigger of the Settings Dialog)
- Added support for [console logs](<logging:PowerShell IDE>) in **PowerShell ISE**

**General**

- Added support for Vault 2023
- Updated powerVault to version: [23.0.1](<powervault:change_logs/powervault_v23:v23.0.1>).\
  Memory usage is reduced when [$vaultExplorerUtil](<powervault:code_reference/objects/vaultexplorerutil>) gets used in a large number of jobs (see [22.0.9](<powervault:change_logs/powervault_v22:v22.0.9>)).

**Fixed**

- Vulnerability in [](</logging>) configuration files by updating *log4net* to v2.0.14 ([CVE-2018-1285](<https://www.cvedetails.com/cve/CVE-2018-1285/>))
- Issue with [ColoredConsoleAppender](</logging>) that caused [powershell remote hosts](<https://docs.microsoft.com/en-us/dotnet/api/system.management.automation.runspaces.runspacefactory.createoutofprocessrunspace>) to crash when appender was logging to console


[powerJobs Settings Dialog]: <job_configuration:powerjobs settings dialog>
[Job Settings]: <job_configuration/job_settings_tab:job settings tab>
[Job Triggers]: <job_configuration/job_triggers_tab:job triggers tab>