Customization and Upgrade
When upgrading to a new version of DPM, different customizations are impacted differently:
Custom Entities
Custom entities that you have created, such as projects, Things, and mashups for custom building blocks, are not impacted by the upgrade. Only PTC-provided files are upgraded.
Upgrades are not automatically applied to custom entities. Review changes to areas of the product that you have customized to determine if you want to apply those changes to your custom entities. Also review the deprecation information to see if any of your customizations are impacted. For more information, see Digital Performance Management 1.2.0 Release Notes and Deprecated Entities, Services, and Other Content.
Localization Table Changes
The localization tables are overwritten when an upgrade is installed. If you have customized any localization tokens, export the customized localization tables before performing an upgrade, and import them back after the upgrade is complete to retain your modifications.
For more information, see Changing User Interface Strings.
 |
If you have customized any of the DPM Administration mashups, be aware that localization tokens previously used in those mashups have been deprecated and replaced in DPM 1.2. For more information, see Deprecated Entities, Services, and Other Content.
|
|
|
Translations for certain database values, such as job order statuses, metric names, and reason category names, are localized using database tables rather than the localization table functionality in ThingWorx Composer. These strings cannot be customized by changing tokens in the ThingWorx Composer localization tables, and are not included when those localization tables are exported. Updates to the translated values provided by PTC can be included in an upgrade. Any translations that you have provided for customer-created reason code names and descriptions are not impacted by an upgrade.
|
Configurations
Settings that you have made on Configuration pages of PTC-provided entities are retained after an upgrade. For example, if you have replaced a modular mashup with a custom mashup, or customized the DPM menu, those configuration settings are retained.
Modified Stored Procedures
Customers should not directly modify the database. The stored procedures and functions in the database that are provided by PTC can be overridden during an upgrade, resulting in the loss of any changes.