powerPLM v27

v27.0.2

22-04-2026

Features

General

  • Added support for Vault 2027

  • The powerFLC Configuration Manager dialog, previously available from the Vault Client Tools menu, has been removed.
    Now there is only one central powerJobs Settings dialog accessible on Job Processor environments.

  • Sample workflows “Transfer Item BOMs” and “Change Management” are no longer installed by default. The scripts and modules are now available on GitHub: https://github.com/coolOrangeSamples/powerflc-samples.

  • Removed powerFLC.log4net and powerFLC.log (including “%LocalAppData%\coolOrange\powerFLC” directory). Logging is now handled via powerGate.log4net, with all logs going to powerGate.log.

  • Renamed powerFLC to powerPLM

  • Updated Licensing to version: 18.4.11

  • Internal refactoring of the setup and installation process.

Breaking Changes

Removed Configuration Manager dialog and related Cmdlets
The powerFLC Configuration Manager dialog is no longer available on Job Processor environments.

Centralized Logging Configuration
The separate log4net configuration files and the dedicated powerPLM log file are no longer used. Logging is now fully managed via the central powerGate.log4net configuration. If you previously customized logging via powerPLM.log4net, please migrate your settings to the central configuration file.

Therefore your Tenant name, Client Id, Client Secret, and System User Email (if used) can no longer be configured and also the Connect-FLC [-UseSystemUserEmail] overload has been removed.
These details must now be specified directly in your scripts:

Connect-FLC -Tenant '{YOUR TENANT}' -ClientId '{YOUR AUTODESK APP CLIENT ID}' -ClientSecret '{YOUR AUTODESK APP CLIENT SECRET}' <# if used: -UserId '{YOUR SYSTEM USER EMAIL}' #>

Since the automatic $workflow variable is no longer available in job scripts:

  • Add your Workflow Settings into #region Settings to keep them configuratble via the powerJobs Settings dialog. Replace occurrences like $workflow.Settings.'My_Settings_Name' with $My_Settings_Name.

  • Specify the previous Vault Entity Type as # JobEntityType = ...

  • Replace $workflow.FlcWorkspace with '{previously configured Workspace Name}' (find all -Workspace ... parameters in your job script)

  • Replace $workflow.FlcUnique with '{previously configured Fusion Lifecycle Field in Unique Identifier section}'

  • Replace $workflow.VaultUnique with $vaultEntity.Your_Vault_Property

  • Remove checks like:

    if (-not $workflow) {
    throw "Cannot find workflow configuration with name '$($job.Name)'"
}

Also the functions GetFlcProperties and GetMappedVaultChangeOrderValuesFromFlcItem have been removed. All Field Mappings must now be hard-coded in your job scripts:

  • Remove usages like $workflow.Mappings | Where-Object { $_.Name -eq "Vault Item -> FLC Item" }).FieldMappings

  • Replace calls like $properties = GetFlcProperties -MappingName "Vault Item -> FLC Item" -Entity $vaultItem with, for example:

    $properties = @{'Number' = $vaultItem._PartNumber; ... }`.

If your configuration previously mapped to PowerShell functions, these must now be refactored directly into the previous hashtable, because the file “%ProgramData%\coolOrange\powerJobs\Modules\coolOrange.powerFLC.Workflows.MappingFunctions.psm1” has been removed.


Modules coolOrange.powerFLC.Workflows* are no longer installed
In addition to our sample workflow jobs, even their Modules are no longer installed by default.
Download the Modules from GitHub to continue using the following functions in your job scripts:

  • coolOrange.powerFLC.Workflows.Common.psm1:
    Add-VaultChangeOrderComment, Add-ItemAssocPropertiesToBomRows, Merge-VaultBomRowsByNumber,
    GetFLCItemIdFromUrn, GetFLCWorkspaceIdFromUrn, GetFLCItemVersionUrns,

  • coolOrange.powerFLC.Workflows.Extensions.psm1:
    GetGridRowData, Get-FLCGridColumns, Get-FLCGridRows, Add-FLCGridRow, Update-FLCGridRow, Remove-FLCGridRow, Update-FLCGrid

  • coolOrange.powerFLC.Workflows.Async.psm1:
    InvokeAsync, WaitAll


Renamed Powershell module
Because also the powerFLC module has been renamed to powerPLM, existing Import-Module powerFLC statements will no longer work and should be removed.


Re-Activation after Upgrade (only if no Customer Key is stored)
If powerGate is already activated on your workstations or Job Processor, no action is required after the upgrade.

If no Customer Key is entered in the License Manager and the previous version was activated using a powerPLM (powerFLC) serial number or via offline activation, a 30-day powerGate trial will start after the upgrade.

To continue using your Fusion Manage integration without interruption, simply enter your Customer Key to activate coolOrange products.
Your powerGate license (which may be newly generated for you) will be retrieved automatically.

For command-line activation, please note that “C:\Program Files\coolOrange\Modules\powerFLC\License.exe” has been removed.
Please use C:\Program Files\coolOrange\powerGate\License.exe instead.