This article offers an overview of the breaking changes and the recommended changes so that your customization still works after an upgrade.


When upgrading a product from e.g. version v19 to v21 make sure to follow the steps to upgrade to the latest v19 version first, then follow the steps for upgrading to v20 and finally to v21.


powerJobs Processor

Upgrade toRequired changes
v17

Follow the manual steps in this article

v18

Custom jobs should be updated to use $job object instead $powerJobs.Job

v19

Custom jobs should be updated to use the Write-Host instead Add-Log


Additionally replace $result.ErrorMessage with with $result.Error.Message in all the scripts and modules

v20

Register the Serial Number for v20 products (and later) on your JobProcessor environment


v21

The Serial Number or Activation File has to be registered again on your JobProcessor environment


Custom jobs should be updated to use the functions from the Applications module instead Get-PowerJobs


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


powerEvents

Upgrade toRequired changes
v20

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

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


powerVault

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


powerGate

Upgrade toRequired changes
v17

Customization has to be updated in locations using Connect-Erp, Disconnect-ERP, Get-ERPServices, Get-ERPObject, Get-ERPObjects, Remove-ERPObject, Update-ERPObject, Add-ERPObject, Update-ERPObject and Add-ERPObject


Usages for cmdlets like Get-ERPConnectionStatus, Resolve-ERPObject, Get-ERPEntities, Add-ERPDir, Update-ERPDir and powerGateErrors variable have to be removed in the scripts


PowerShell scripts containing Show-ErpWindow have to use Show-BomWindow instead.

See: breaking changes

v19

When upgrading to this version remove the StoredLayout files


Customizations with global PowerShell variables or other cachings may have to be updated in when conflicts arise because required BomWindow functions are executed in current runspace


Scripts expecting Get-BomRows to be called automatically after Add-BomWindowEntity  have to be adapted

See: breaking changes

v20

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

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

Export your configuration for the standard workflows from the previous version and import it in the new version


powerFLC

Upgrade toRequired changes
v21

Update scripts to use 'Import-Module powerFLC' instead of 'Import-Module vaultFLC'


The Serial Number or Activation File has to be registered again on your Vault environments


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

See breaking changes

v21.1

The configuration for connecting to Fusion Lifecycle has to be entered again


To use the standard workflows recreate them in the Configuration Manager


To still have the removed Administration tab download it from GitHub.

See breaking changes


powerGateServer

Upgrade toRequired changes
v20

Register the Serial Number for v20 products (and later) on your server environment

v21

Plugins using the coolOrange.Logging.dll assembly need to be re-built


powerJobs Client

Upgrade toRequired changes
v20

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

v21

Rename your config file to 'powerJobs Client.config' if it was customized.


The Serial Number or Activation File has to be registered again on your Vault environments


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

See breaking changes


See Also

coolOrange Download Zone