When updating to the current version execute all the steps after your current version to the end. For example when updating from v20.0.1 to current version start with instructions for 21.0.3.
Update to v27.0.2
Configuration Manager has been removed
The powerFLC Configuration Manager has been removed and is no longer available after upgrading to powerPLM v27.
The legacy Configuration Manager is still available on GitHub for reference, but it is no longer supported and should be replaced by the powerJobs Settings dialog for Job Processor environments.
If your existing workflows rely on the Configuration Manager, migrate the configuration into your job scripts before upgrading.
Job Entity Type
If your job doesn't have an entity type yet you should add it as early in the script as you can. This should always be in the format
# JobEntityType = <EntityType>
For example for an item job it would be
# JobEntityType = ITEM
Valid entity types are ITEM, FILE, FLDR, CUSTENT, CO
Connect-FLC
Specify the Tenant, Client ID, Client Secret and, if required, the System User directly in the Connect-FLC call.
Also rename Connect-FLC to Connect-PLM
Connect-PLM -Tenant '{YOUR TENANT}' -ClientId '{YOUR AUTODESK APP CLIENT ID}' -ClientSecret '{YOUR AUTODESK APP CLIENT SECRET}' <# if used: -UserId '{YOUR SYSTEM USER EMAIL}' #>
Workflow Settings
If your jobs don't have a settings region yet create one as shown in the powerJobs Processor documentation.
Afterwards you must create the settings from your settings dialog within your settings region
If your workflow setting is assigned to another variable just move it up to your new settings region instead of creating a new variable
Example for migrationg the "Upload Item Attachments" workflow setting
Create a new variable in the settings region. In this case it is called $uploadItemAttachments and it is set to $true
Then search in your script for all usages of the old setting. You should find most of them by searching for the setting name. in this case "Upload Item Attachments". The settings are always accessed via the workflows "Settings" property.
You have to replace the complete
$workflow.Settings.'Upload Item Attachments'
expression with your new variable
Replace workspace and unique identifier
Replace $workflow.FlcWorkspace with value from "Fusion Lifecycle Workspace"
Replace $workflow.FlcUnique with value from "Fusion Lifecycle Field"
Replace $workflow.VaultUnique with value from "Vault Property"
Example for $workflow.FlcWorkspace
Remove checks for the $workflow object
Search for the condition that checks if $workflow exists and remove it completely
Remove checks for field mappings
Search for "$fieldMapping in ($workflow.Mappings". If you find code like in the image below remove it completely. There might be multiple such blocks in your script or none at all
Remove any leftover $workflow references
When you are done you shouldn't have any $workflow variables in your script anymore!
Lastly search your script for $workflow and remove or replace any leftover references that might not have been handled by previous steps.
Replace GetFlcProperties
For the Sample.TransferItemBOMs.ps1 job the field mappings are read by the function GetFlcProperties.
It is defined in coolOrange.powerFLC.Workflows.Common.psm1 which will not exist anymore after the update.
GetFlcProperties must be replaced. The field mappings should be hard-coded in the script.
"Vault Item -> FLC Item" pre replacement
"Vault Item -> FLC Item" post replacement
"Vault primary Item-File Link -> FLC Item" pre replacement
"Vault primary Item-File Link -> FLC Item" post replacement
Field mapping functions are defined in coolOrange.powerFLC.Workflows.MappingFunctions.psm1 which will also be removed. If you use any of those functions in your mappings you have to copy those functions into your job.
Copy every function that is used within the mapping from coolOrange.powerFLC.Workflows.MappingFunctions.psm1 into your job.
Replace GetMappedVaultChangeOrderValuesFromFlcItem
For the Sample.SyncChangeOrders.ps1 job the field mappings are read by the function GetMappedVaultChangeOrderValuesFromFlcItem.
It is defined in coolOrange.powerFLC.Workflows.Common.psm1 which will not exist anymore after the update.
GetMappedVaultChangeOrderValuesFromFlcItem must be replaced and the mappings should be hard-coded in the script.
Sample workflows and modules are no longer installed
The sample workflows Transfer Item BOMs and Change Management are no longer installed by default.
Download the modules from https://github.com/coolOrangeSamples/powerflc-samples/tree/master/Sample.TransferItemBOMs/Modules and put them into C:\ProgramData\coolOrange\powerJobs\Modules
PowerShell module renamed
The PowerShell module has been renamed from powerFLC to powerPLM.
Remove all statements like
Import-Module powerFLC
as the powerPLM module is loaded automatically.
Logging configuration
Logging is now managed centrally by powerGate.
If you previously customized powerFLC.log4net (or powerPLM.log4net), migrate your settings to powerGate.log4net.
The dedicated powerFLC.log, powerPLM.log and the %LocalAppData%\coolOrange\powerFLC log directory are no longer used.
Licensing changes
Starting with v27, the powerPLM Cmdlets are included with powerGate and are covered by a single powerGate license.
If powerGate is already activated using a Customer Key, no further action is required.
If your previous installation was activated using a powerPLM (powerFLC) serial number or offline activation and no Customer Key is stored, a 30-day powerGate trial will start after the upgrade. In this case, enter your Customer Key after upgrading to activate your powerGate license.
If you use command-line activation, replace
C:\Program Files\coolOrange\Modules\powerFLC\License.exewith
C:\Program Files\coolOrange\powerGate\License.exeUpdate to 24.0.3
This version requires powerVault 24.0.5 to generate the Vault thin and thick client links properly.
Update to 22.0.22
If the Filter parameter of the Get-FLCItems Cmdlet includes spaces, they must be enclosed in double quotes or it might not work properly:
Get-FLCItems ... -Filter "owner=`"Doe John`""
Update to 22.0.21
The $tenant variable which was used in the Workflows for connecting to fusion 360 Manage was removed. It can be replaced by using the Connect-FLC Cmdlet since it now automatically retrieves the configured tenant settings if the application is connected to Vault. The parameters for the Connect-FLC Cmdlet can still be used:
Previous:
Connect-FLC -Tenant $tenant.Name -ClientId $tenant.ClientId -ClientSecret $tenant.ClientSecret -UserId $tenant.SystemUserEmail
Now:
$connected = Connect-FLC
OR
$connected = Connect-FLC -Tenant 'yourtenant' -ClientId 'yourClientId' -ClientSecret 'yourClientSecret' -UserId 'yourEmail'
Update to 22.0.17
When upgrading from an earlier version it is recommended to uninstall the previous version before installing the latest version.
Update to 22.0.14
The "Transfer Item BOMs" workflow configuration must be imported again.
To keep the customizations for the "Transfer Item BOMs" workflow follow these steps:
- Rename the Field mapping group "Item Field Mapping" to "Vault Item -> FLC Item"
- Rename the Field mapping group "BOM Field Mapping" to "Vault BOM -> FLC BOM"
- Rename the Field mapping group "Grid Field Mapping" to "Vault BOM -> FLC Grid"
- Create a new Field Mapping group named "Vault primary Item-File Link -> FLC Item".
All the functions used in the "Item Field Mapping" group that start with "GetPrimaryFile" have to be added to this Field Mapping group. Instead of the functions the corresponding setting can be set in the "Vault File property" column.
The following functions were removed.
- GetPrimaryFileName
- GetPrimaryFileFolder
- GetPrimaryFileVersion
- GetPrimaryFileProvider
- GetPrimaryFileCategory
- GetPrimaryFileState
- GetPrimaryFileRevision
- GetPrimaryFileProject
Save your coolOrange.powerFLC.Workflows.MappingFunctions.psm1 module before upgrading powerPLM(powerFLC) in order to still have your custom functions and the removed functions.
Update to 21.1.2
Upgrading other products to v21 may be required, as described in this article
The information for connecting to Fusion Lifecycle has to be entered again
The standard workflow have been removed. To use the standard workflows from previous versions they have to be recreated in the Configuration Manager and a custom workflow job must also be created
The Administration tab was removed. To still have the removed Administration tab you can download it from GitHub
Export your configuration for the standard workflows from the previous version and import it in the new version
Update to 21.0.3
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
Update to 20.0.1
When updating from an older version it is recommended to uninstall the old version before updating