powerEvents v24




  • Updated powerVault to version: 24.0.5







  • Folder structure for Client Customizations has been simplified

  • The PowerShell runspace, that loads these client customizations, got a friendly name: “coolOrange”.
    This makes it easier to debug script executions by attaching a Powershell debugger to the Vault application.

  • Client Customizations can now be easily distributed from any environment, whether it’s a development machine or a productive workstation


  • Removed the non-intuitive “Events” directory, as it also allows PowerShell scripts to extend the user interface of Vault Client, Inventor or realizing entire ERP integrations.
    Therefore, Scripts are now placed directly in the directory “C:\ProgramData\coolOrange\Client Customizations” and Modules in the subdirectory of the same name.

  • Minor adjustments in text references to “event scripts” in messages for logs and Error Message Boxes

  • Windows Permissions for directory “C:\ProgramData\coolOrange” were changed to Read, Write & Delete for Everyone to allow synchronizing scripts and modules

  • The Publish-Customizations.ps1 script has been moved to “C:\ProgramData\coolOrange” but still only supports the distribution of client customizations

  • During Vault application startup, if distribution problems occur with client customizations, the Error Message Box now displays additional details that help in resolving these issues more effectively

Breaking Changes

Change paths in Customization distribution mechanisms

If you or your IT department use a distribution mechanism to automatically install or update scripts and modules on all workstations, note that the paths where they are stored must be changed!




C:\ProgramData\coolOrange\Client Customizations


C:\ProgramData\coolOrange\Client Customizations\Modules

When updating to this version (or newer), all scripts and modules from the old directory “C:\ProgramData\coolOrange\powerEvents” are automatically moved to the correct structure.
In addition, powerEvents reminds and assists in loading customizations also from this old directory (for another two major versions).
However, please be aware that related functionalities - such as the automatic reloading of scripts and the build-in distribution mechanism - unfortunately no longer work for the obsolete directory.




  • Updated Licensing to version: 18.3.1
    This significantly improves the performance of loading powerEvents during Vault logins when a Standalone license is registered for the product.




  • Script changes can now be saved while modal dialogs are open, resulting in a smoother debugging and development experience.
    For example, if changes are saved while an Error Message Box or other blocking windows are displayed, the dialog box can be closed and the current changes will automatically take effect at the next execution.

  • For active Vault Client tabs created with Add-VaultTab, the -Action parameter is now automatically re-executed when changes are automatically reloaded.


  • Issue where the automatic reloading of script changes stopped working if a reload did not complete. Reasons for this could be concurrent PowerShell executions or blocked runspaces.
    Restarting the host application is now no longer required because it ensures that all recent changes are reloaded, even if modal dialogs are open when saving.

  • Changes to customization scripts are no longer reloaded on MTA background threads, which prevents unexpected “System.InvalidOperationException: The calling thread must be STA …” errors when running scripts that use WPF elements.

  • Issue where Error Message Boxes appeared in the background of the host application




  • Added support for Vault 2024

  • Updated Licensing to version: 18.2.29

  • End User License Agreement (EULA) has changed