# powerEvents v23

## v23.0.20

`17-04-2023`

**General**

- Updated powerVault to version: [23.0.15](<inv:powervault#change_logs/powervault_v23:v23.0.15>).

**Fixed**

-  Issue when using `finally` statements in script blocks or PowerShell functions, where the execution of *-Action* parameters in [](</code_reference/commandlets/register-vaultevent>), [](</code_reference/commandlets/add-vaulttab>), [](</code_reference/commandlets/add-vaultmenuitem>) and [](</code_reference/commandlets/add-inventormenuitem>) cmdlets failed with *System.NullReferenceException* even before the actual finally block could execute
- Display issue in the Error Message Box where *System.Management.Automation.RuntimeException* was displayed for all [terminating errors](<client_customizations:errors>) instead of their actual exception type


## v23.0.19

`06-03-2023`

**Features**

- **New cmdlet**: [](</code_reference/commandlets/add-inventormenuitem>) to register menu items in Inventor ribbons with custom Actions that are invoked when the menu items are clicked.

**Fixed**

- Issue where Vault Data Standard (VDS) customizations executed significantly slower, **after** registered [VaultEvents](</code_reference/objects/event_mappings>) were triggered from the VDS customization


## v23.0.17

`22-02-2023`

**General**

- Updated powerVault to version: [23.0.14](<inv:powervault#change_logs/powervault_v23:v23.0.14>).

**Fixed**

- Issue in the [](</code_reference/commandlets/add-vaulttab>) cmdlet where the Vault Client crashed when terminating exceptions occurred in UI events, such as ScriptBlocks invoked on `$button.add_Click({ ... })` events

## v23.0.16

`14-02-2023`

**General**
- Updated powerVault to version: [23.0.11](<inv:powervault#change_logs/powervault_v23:v23.0.11>).

**Features**
- [](</code_reference/commandlets/add-vaultmenuitem>): Added support to add menu items to the context menu of Vault **Folders**

**Fixed**

- Issue where context menu items were not displayed when the [](</code_reference/commandlets/add-vaultmenuitem>) cmdlet was used for multiple different [locations](<code_reference/commandlets/add-vaultmenuitem:VaultExplorerMenu>)
- Issue in [](</code_reference/objects/event_mappings/file_events/updatefilestates>)*_Restrictions* and *_Pre* events where properties of `$files` parameter instances return either empty or wrong values when accessed from outside the registered function or Scriptblock.
- Issue where uninstalling product also uninstalled [powerVault](<inv:powervault#index>), although it was still needed by other products, e.g. [powerJobs Processor](<inv:powerjobs_processor#index>).

## v23.0.14

`01-02-2023`

**General**

- Significant performance improvements when large Inventor assemblies are Checked-in to Vault and [](</code_reference/objects/event_mappings/file_events/addfile>)- or [](</code_reference/objects/event_mappings/file_events/checkinfile>) events are registered.\
  For these events, unncecessary Vault API calls will be prevented when `$dependencies`,`$attachments` or `$fileBom` parameters are not used.
- Product-wide performance improvements by configuring the log level 'INFO' for the [\<root> logger](<logging:logfile>) to avoid automatically generated DEBUG logs if not configured.
- Updated powerVault to version: [23.0.10](<inv:powervault#change_logs/powervault_v23:v23.0.10>).


## v23.0.13

`12-01-2023`

**Fixed**

-  Issue where new "low-level Vault connection" was created against Vault Data Server (ADMS), when working in environments with dedicated/separated Vault File Server (AVFS).


## v23.0.12

`15-12-2022`

**General**

- Behavior of `Add-VaultMenuItem` when called multiple times for same menu item has changed: Instead of ignoring subsequent calls for same menu item, [](</code_reference/commandlets/add-vaultmenuitem>) cmdlet now updates the passed `-Action` for the menu item.

**Features**

- [](</code_reference/commandlets/add-vaultmenuitem>): Added support to add menu items to the Vault Explorer's **Tools menu**


## v23.0.11

`07-12-2022`

**Features**

- **New cmdlet**: [](</code_reference/commandlets/add-vaulttab>) to register a new tab for a specific entity type in the Vault Explorer with an Action that is invoked when the tab is clicked.
- Simplified [enabling and disabling](<getting_started:activating a sample script>) customization scripts by providing a *"./Disabled"* subdirectory where scripts can be moved to, instead of uncommenting or commenting the contained `Register-VaultEvent ...` lines.

**Fixed**

- Issue that manually disabled/enabled Sample- and standard [scripts](<client_customizations:scripts>) are automatically reverted after installing [Updates](</installation>).\
  **Note:** This will only affect future versions. If sample scripts have been manually enabled (uncommented `Register-VaultEvent ...` lines), they can be moved to *%ProgramData%/coolOrange/powerEvents/Events* directory after updating from [v23.0.9](<change_logs/powerevents_v23:v23.0.9>) or earlier.
- Issue that [LoginVault_Post](</code_reference/objects/event_mappings/connection_events/loginvault>) event actions were not executed before those of other event registrations
- Issue where updating a property mapped to an AutoCAD property with [](<inv:powervault#code_reference/commandlets/update-vaultfile>) in an event causes the Vault Client to freeze.

**General**

- Changed type of property *Name* on [](</code_reference/objects/event/>) results from *'powerEvents.Cmdlets.VaultEvent'* to *'String'*.


## v23.0.9

`27-10-2022`

**General**
- Updated powerVault to version: [23.0.8](<inv:powervault#change_logs/powervault_v23:v23.0.8>).

**Features**

- **New VaultEvent**: [LoginVault_Post](</code_reference/objects/event_mappings/connection_events/loginvault>) which gets raised after successfully signing in to Vault.

**Fixed**

- Issue with [](</code_reference/objects/event_mappings/file_events/addfile>)- and [](</code_reference/objects/event_mappings/file_events/checkinfile>) events not getting executed when files with empty BOMs (and *copyBom* parameter disabled) are checked into Vault.\
   This applies to all non-modelling files (e.g. drawings, presentation files or automatically generated design visualization files) that are checked in through Inventor or AutoCAD.

## v23.0.7

`29-09-2022`

**General**

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

**Fixed**

- Issue where repair via setup was not possible if powerVault was previously uninstalled
- Issue where powerVault was listed twice in Programs and Features after upgrading powerVault

## v23.0.6

`23-08-2022`

**Features**

- The `-Action` parameter of the [](</code_reference/commandlets/add-vaultmenuitem>) cmdlet is invoked with [powerVault entities](<inv:powervault#code_reference/objects>) as parameter, which provide all entity properties without having to implement custom logic to retrieve them

## v23.0.5

`28-07-2022`

**Features**

- **New cmdlet**: [](</code_reference/commandlets/add-vaultmenuitem>) to register menu items with custom actions in the Vault Explorer
- **New client customization**: [SubmitJobsOnVaultMenuItemClick.ps1](</client_customizations/SubmitJobsOnVaultMenuItemClick>) to submit jobs from the context-menu (right-click menu) in Vault when configured in the [powerJobs Settings Dialog](<inv:powerjobs_processor#job_configuration/job_triggers_tab:trigger job manually by context menu item>).

**General**

- Updated powerVault to version: [23.0.6](<inv:powervault#change_logs/powervault_v23:v23.0.6>).\
  This allows custom applications to execute events registered in customization [scripts](</client_customizations/>) again when using powerVault [v23.0.4](<inv:powervault#change_logs/powervault_v23:v23.0.4>) or later (see fix [v23.0.1](<change_logs/powerevents_v23:v23.0.1>)).\
  Also, warning logs like *"Creating a low level connection to the server"* should no longer appear.


## v23.0.1

`20-04-2022`

**Features**

-  Added support for Vault 2023
-  Added support for [console logs](<logging:coloredconsoleappender>) in **PowerShell ISE**

**General**

- Updated powerVault to version: [23.0.1](<inv:powervault#change_logs/powervault_v23:v23.0.1>).\
  Memory usage is reduced when a large number or frequently executed Vault events are [registered](</code_reference/commandlets/register-vaultevent>) (see [22.0.9](<inv: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
- Issue where the _Action_ from the [Register-VaultEvent](</code_reference/commandlets/register-vaultevent>) was not executed when Vault event was triggered from custom application
- “Page not found” error page opens after clicking Help button in Control Panel → Add or Remove Programs