Skip to main content

 –

Running the Pre-Upgrade Check

Suggest edit Updated on January 22, 2021

Assess whether your system is ready for an upgrade to the latest version by adding the Pre-Upgrade Check component to your Pega Customer Decision Hub application, and then running a series of checks.

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-upgrade 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.
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us