Update powerEvents to current version

Summary of changes that need to be done when updating powerEvents to current version

When updating to the current version execute all the steps after your current version to the end. For example when updating from v20.0.7 to current version start with instructions for 21.0.7.

 

powerEvents also installs and updates powerVault. powerVault changes described in this article also apply.

Update to 20.0.7

Register the Serial Number for v20 products (and later) on your Vault environments

See: breaking changes

Update to 21.0.7

Upgrading other products to v21 may be required, as described in this article

Remove try catch blocks that were made to notify users about exceptions in script blocks or functions passed to the -Action parameter of Register-VaultEvent calls since powerEvents now displays error notifications

See: breaking changes

Update to 22.0.5

Retrieve linked properties of ChangeOrder Items using the "Record_" prefix for AddChangeOrder or CommitChangeOrder event

Update to 24.0.4

Change paths in Customization distribution mechanisms

All the powerEvents scripts are now stored in a new location.

If you or your IT department uses a distribution mechanism to automatically install or update scripts and modules on all workstations the paths where the powerEvents scripts are located must be changed!

Scripts

Prior to 24.0.4: C:\ProgramData\coolOrange\powerEvents\Events
New Path: C:\ProgramData\coolOrange\Client Customizations
Modules
Prior to 24.0.4: C:\ProgramData\coolOrange\powerEvents\Modules
New Path: C:\ProgramData\coolOrange\Client Customizations\Modules

Also make sure to update paths in your scripts if they happen to reference "C:\ProgramData\coolOrange\powerEvents" or any sub directory

Single workspace
When installing powerEvents 24.0.4 or any newer version the the scripts and modules of the current installation will be automatically moved from "C:\ProgramData\coolOrange\powerEvents" into the new directory structure.

Update to 25.0.11

Generally, no breaking changes are expected with upgrades from previous versions with powerEvents functionality.

However, if you are using customizations for Inventor 2025 or AutoCAD 2025 there might be breaking changes due to the change to PowerShell 7 

In that case, you’ll need to adjust these customization scripts to ensure compatibility with PowerShell 7.

Vault 2025 still uses Windows PowerShell. If you are using shared modules it might be necessary to split some code into PowerShell7 and Windows PowerShell 5.1 variants

For more details, Microsoft provides information on missing cmdlets and other potential differences between Windows PowerShell and PowerShell 7.4.

Update to 26.0.1

If you are using Vault 2026, Inventor 2025/2026, AutoCAD 2025/2026 all scripts will now run with PowerShell 7.

In that case, you’ll need to adjust these customization scripts to ensure compatibility with PowerShell 7.

For more details, Microsoft provides information on missing cmdlets and other potential differences between Windows PowerShell and PowerShell 7.4.

Update to 26.0.8

Custom Applications Require Configuration

With this change, powerEvents now respects the powerJobs Client - Configuration. As a result, only the default applications are supported out of the box.
If you are using custom applications, you must extend the configuration to include the desired applications.