powerGate v25
v25.0.15
03-04-2025
Features
New Show-BOMWindow parameter -NoWait: Opens the BOM Window non-modally,
allowing Vault users to continue their work while long-running Check or Transfer operations proceed in the background.
Fixed
In the BOM Window, repeated “BOM Check” operations incorrectly changed “Removed” ERP rows to “New”, causing an increasing number of rows with each run.
(The now automatically executed line$vaultBom.Children | Where-Object { $_._Status -eq 'Remove' } | ForEach-Object { $_ | Remove-BomWindowEntity }
has been removed in Sample.Tab-File-ErpBom and Sample.Tab-Item-ErpBom)Fixed a race condition in the .NET library where
GetErpObject(<Keys>)
existance checks sometimes failed with an exception when called simultaneously from multiple threads
General
Connect-ERP -OnConnect parameter $settings has been extended with
add_BeforeRequest
andadd_AfterResponse
functions,
allowing easy handler attachment in PowerShell scripts and parallel execution across different Runspace threadsEnhanced “ERP BOM” sample tabs to fully support the non-modal opening of the BOM Window (Sample.Tab-File-ErpBom and Sample.Tab-Item-ErpBom)
Added flag $IsBomWindowRunning which indicates if a BOM Window is displayed
Updated powerEvents to version: 25.0.24:
Custom menu items can now be easily found in a submenu named “COOLORANGE” instead of “powerJobs Client”.
However it’s also possible to specify your own submenus for Add-VaultMenuItem (with HTML styling), and also custom Vault folder tabs can now be created with Add-VaultTab.Custom menu items and tabs can now be created for Vault Custom Objects.
v25.0.13
15-01-2025
Fixed
Compatibility issues after upgrading to v25 due to the renaming of the
powerGate_256px.ico
file, e.g. causing the opening of custom ERP dialogs - such as Create-, Change-, Insert- and Link ERP Item - to fail
(see breaking change in v25.0.5)
General
Updated powerEvents to version: 25.0.20
Improved logging of PowerShell ERRORs (e.g in cmdlets, -OnConnect script blocks, BOM Window functions) which are no longer followed by redundant WARN logs.
More detailed logs for exceptions in the coolOrange.PowerShell.Cmdlets namespace can now be enabled by changing to DEBUG.
v25.0.9
05-12-2024
Fixed
Updated Licensing to version: 18.4.7.
This resolves issues with failing command-line activations, the no longer working “powerGate Information” shortcut, and rare ERP connection errors when trying to display possible license notifications.Updated powerEvents to version: 25.0.16.
This solves issues with automatically reloaded changes in ERP integration scripts that were saved while modal dialogs are open, such as Error Message Boxes, Connection Error Dialogs, the BOM Window or Inspector dialogs.Issues related to Auto-Importing the powerGate module in PowerShell on environments where the module was never explicitly imported before and on environments where it was imported and used before.
v25.0.5
10-10-2024
Features
Updated Licensing to version: 18.4.2.
The product can now be easily activated on new environments via a single customer key - together with all other coolOrange products in your subscription.Added support for .NET 8 applications, enabling ERP integrations from .NET (core) applications like Inventor 2025 and cmdlets in PowerShell 7
General
Added support for Vault and Inventor 2025
The Windows Start Menu now contains the coolOrange-wide Licence Manager instead of the powerGate License Information shortcut
Shared third-party Libraries (e.g. log4net, PostSharp Diagostics and Infragistics) are no longer installed into the GAC but are now merged to avoid conflicts with other products and plugins
Introduced a new product icon that’s simpler and easy to recognize within our product portfolio
Changed color for WARN log messages in Console to make them easier to read
Updated minimum required .NET Framework version to 4.7.2
Breaking Changes
Renamed Icon Resource
The resource for the powergate logo has been renamed from powerGate_256px.ico
to powerGate_256.ico.
This change may affect ERP integrations that rely on our samples from previous versions. For example, opening ERP dialogs will fail (see details in v25.0.13).
To resolve this issue, update the following pack-URI in all affected xaml files:
Previous |
Now |
---|---|
|
|
Error handling changed for ERP Cmdlets in psm1 Modules
By default, ERP cmdlet failures don’t terminate the script execution, even when $global:ErrorActionPreference is set to Stop!
However, from this version onwards, ERP Cmdlets in psm1 files will follow the module’s own error settings (each module has its own scope for $PSDefaultParameterValues[*:ErrorAction]
).
Therefore this mainly affects powerGateTemplate base ERP integrations implemented with Vault Data Standard, where many unexpected error dialogs may now appear.
It is recommended to avoid using psm1 modules if possible.
Alternatively, to restore the previous behavior consistenly, add this line to every psm1 script that makes use of ERP cmdlets:
$script:PSDefaultParameterValues = $global:PSDefaultParameterValues
Possible Breaking Changes with Inventor 2025
Generally, upgrades are fully compatible with PowerShell 7 and do not require any changes!
Only in rare cases, adjustments may be necessary for powerEvents based ERP integrations.
For more details, Microsoft provides information on missing cmdlets and other potential differences between Windows PowerShell and PowerShell 7.4.