Pega Customer Service Upgrade Checker
Before you update to a new minor version of Pega Customer Service for Insurance, run the Pega Customer Service Upgrade Checker to check whether your application includes overrides to final rules, or rules that Pega has deprecated or withdrawn. You can then fix the overrides, and remove the deprecated and withdrawn rules. For more information, see Pega Customer Service Upgrade Checker.
The Pega Customer Service Upgrade Checker was added to the Pega Customer Service for Insurance applications in version 8.3.
- For Pega Customer Service industry applications:
- If updating from version 8.2 or earlier, first update your application to the latest version, and then run the Pega Customer Service Upgrade Checker.
- If updating from version 8.3 or later, run the Pega Customer Service Upgrade Checker before you update.
- For the Pega Customer Service base application (without an industry
application):
- If updating from version 7.31 or earlier, first update your application to the latest version, and then run the Pega Customer Service Upgrade Checker.
- If updating from version 7.4, 8.1, or 8.2, request the hotfix that includes the upgrade checker tool for those versions (called the Pre-Upgrade Checker), and then run the Pre-Upgrade Checker before you update.
- If updating from version 8.3 or later, run the Pega Customer Service Upgrade Checker before you update.
Final rules
A final rule is a locked rule that you should not override in your application because an override interferes with updates or is not allowed for security reasons. Final rules without extensions are infrastructure rules that you should never modify because changes to an infrastructure rule can prevent the application from working correctly. As part of improving the update and implementation processes, Pega has identified and locked many existing rules that were not previously locked.
- If there are no overrides to final rules, the health of your application is displayed as Good.
- If there are overrides to final rules, the health of your application is displayed as Poor.
The effort required to remove overrides depends on the number of overrides that you need to address, and the complexity of each override. Some overrides might be easier to withdraw without any additional re-work, while others might require a redesign of custom features that are delivering business value.
Previous topic Running the Upgrade Checkers Next topic Importing the critical rules list