With the Pre-Upgrade Check component, you can identify the following types of problems that might cause errors or failure during an upgrade:

• Missing hotfixes
• Locked artifact ruleset
• Excessive number of batch database tables
• Customized rules
• Column length for pyDesciption on the PR4_RULE table is not increased to 1000

Prepare your application for an upgrade by identifying and resolving any issues that might make the upgrade unsuccessful.

1. In the header of the Pega Customer Decision Hub portal, click ConfigurationPre-Upgrade Check.
2. On the Pre-upgrade check page, click Run.
   Result: The application displays the results grouped into categories, as shown in the following example:

   

   

3. Review and resolve the reported issues.
   For more information, see Resolving pre-update issues.
4. Run the Pre-Upgrade Check component again by repeating steps 1 through 3.
   When the check returns no more issues, your application is ready for an upgrade.