Customizing the ThingWorx Apps > Upgrade and Customizations
Upgrade and Customizations
When upgrading to a new version of ThingWorx Apps, different customizations are impacted differently:
Direct Edits to Extension Entities
Direct edits to entities provided with the extensions, such as the schedulers and media entities, are overwritten during an upgrade. If these customizations are wanted in the new release, they will need to be re-implemented after the upgrade is complete. For more information, see Customizing the Schedulers and Changing the Logos in the Application Console.
Localization Table Changes
The localization tables are overwritten when an upgrade is installed. To keep your localization table modifications, export the customized localization table before performing an upgrade, and import it back after the upgrade is complete.
For more information see Changing Labels in the Application.
Launch Point Configuration Thing Changes
A new launch point configuration Thing (PTC.Factory.C_LaunchPointConfigurationThing_[ReleaseVersion]) is delivered with the application for each release. Your changes to the launch point configuration Thing for the previous release are not overwritten during an upgrade, but they are not automatically applied in the upgraded extension.
Changes made to a release-specific launch point configuration Thing include, but are not limited to:
LaunchPointEntitySettings changes pointing to customized mashups.
Custom equipment types added to the EquipmentTypeSettings configuration table.
Additional contexts added to the EquipmentContextSettings configuration table.
New connections defined on the RemoteConnectionSettings configuration table.
Compare your launch point configuration Thing from the previous release (PTC.Factory.C_LaunchPointConfigurationThing_[OldReleaseVersion]) with the launch point configuration Thing from the new release (PTC.Factory.C_LaunchPointConfigurationThing_[NewReleaseVersion]). Apply any changes that you want to keep from the previous release to the launch point configuration Thing for the new release.
Duplicate Mashup Changes
Release-specific duplicate mashups are provided with each release for customization purposes. Any customizations you have made to these duplicate mashups are not overwritten during an upgrade, but those customizations are not automatically applied in the upgraded extension.
After reviewing the changes in the upgraded extension, compare your customized release-specific duplicate mashups from the previous release to the mashups provided with the new release. Apply any customizations that you want to keep from the previous release to the duplicate mashups provided in the new release. Change the appropriate LaunchPointEntitySettings entries in the launch point configuration Thing (PTC.Factory.C_LaunchPointConfigurationThing_[ReleaseVersion]) for the new release to point to your new customized duplicate mashup.
To find the release-specific duplicate mashups:
1. In ThingWorx Composer, navigate to Browse > Mashups.
2. In the search field, search for the string "*C_".
3. The release version for each release-specific duplicate mashup is present at the end of the mashup name.
* 
When viewing or editing mashups that are provided with ThingWorx Apps, click No if presented with a message asking if you want to replace deprecated widgets with new widgets.
Tile Changes in the Console Data Table
Changes made for tiles in the release-specific console data table (PTC.FactoryConsole.C_DataTable_[ReleaseVersion]) are retained, but not automatically applied in the upgraded extension. If you want those changes in the upgraded extension, perform the following steps after completing the upgrade:
1. Modify the TilesDataTable entry under LaunchPointEntitySettings in the launch point configuration Thing (PTC.Factory.C_LaunchPointConfigurationThing_[NewReleaseVersion]) to point to the new console data table of PTC.FactoryConsole.C_DataTable_[NewReleaseVersion].
2. Modify the console data table for the new release (PTC.FactoryConsole.C_DataTable_[NewReleaseVersion]) with all changes that were made in the console data table for the old release (PTC.FactoryConsole.C_DataTable_[OldReleaseVersion]).
Changes in the Equipment Relationship Definition Data Table
The PTC.SCA.SCO.DefaultEquipmentRelationshipDefinition data table is overwritten during upgrades. A release-specific version of the data table (PTC.SCA.SCO.C_DefaultEquipmentRelationshipDefinition_[ReleaseVersion]) is provided for making changes to these default equipment relationship definitions. Changes to the release-specific equipment relationship definition data table are not overwritten during an upgrade, but they are not automatically applied in the upgraded extension. If you want those changes in the upgrade extension, perform the following steps after completing the upgrade:
1. Modify the EquipmentRelationshipSettings value on the EquipmentContextSettings configuration table on the launch point configuration Thing (PTC.Factory.C_LaunchPointConfigurationThing_[NewReleaseVersion]) to point to the new equipment relationship definition data table (PTC.SCA.SCO.C_DefaultEquipmentRelationshipDefinition_[NewReleaseVersion]).
2. Modify the data table for the new release (PTC.Factory.C_LaunchPointConfigurationThing_[NewReleaseVersion]) with all changes that were made in the data table for the old release (PTC.Factory.C_LaunchPointConfigurationThing_[OldReleaseVersion]).
For more information, see Defining Equipment Relationships.
Was this helpful?