Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Verifying that Pega Customer Decision Hub is ready for upgrade

Updated on December 20, 2021

This content applies only to Pega Cloud environments

Perform a confidence check of your Pega Customer Decision Hub application in the upgraded, temporary production environment to make a go/no-go decision to accept or abandon the upgrade, and then communicate the decision to Pega Cloud services.

You have 60 minutes to complete the confidence check. This window starts when you receive a notification from Pega Cloud services that the temporary go/no-go system is available.

The go/no-go stage is part of the minor upgrade process. For more information about the process, see Minor upgrade process for Pega Infinity 8.4.x and later and Minor upgrade checklist.

Pega Customer Decision Hub Update Guide
Before you begin: In the upgraded, cloned staging environment, create a test package in the form of a product rule. For more information, see Creating a Pega Customer Decision Hub test package for the go/no-go upgrade stage.
  1. Log in as [email protected] with the default password to the upgraded, temporary production environment.
    The URL to the temporary production environment is available in the My Support Portal and includes the word ephemeral.
  2. In the prompt to change the password, set the new password.
  3. Import the test package (product file) to the temporary production environment:
    1. In the header of Dev Studio, click ConfigureApplicationDistributionImport.
    2. Use the Import wizard to import the product file.
  4. In Dev Studio, open each operator record that you import.
  5. For each record, on the Security tab, configure the basic settings:
    1. Clear the Force password change on next login check box, and then click Save.
    2. Clear the Disable Operator check box, and then click Save.
  6. Log out, and then log back in as an imported operatorone of the operator accounts that you imported with access to Pega Customer Decision Hub.
  7. Flush the D_CDHSubjectDictionary data page:
    1. In Dev Studio, search for and click the D_CDHSubjectDictionary data page.
    2. On the D_CDHSubjectDictionary tab, click ActionsRun.
    3. In the Run window, in the Value field for the DictionaryName parameter, enter CUSTOMER.
    4. Select Flush all instances of this data page before execution, and then click Run.
  8. Launch the Pega Customer Decision Hub portal and ensure that the portal loads properly.
    Important: During confidence testing, you might notice some limitations in the temporary production environment. These limitations are normal and will be cleared after the upgrade is completed:
    • The Next-Best-Action Designer upgrade is pending. You can upgrade the Next-Best-Action Designer at any point after the upgrade to Pega Customer Decision Hub 8.5 is completed. For more information, see Upgrading the Next-Best-Action Designer.
    • In the navigation pane, the Campaigns menu item is missing. The data schema is not fully populated, which is why campaigns are not available at this stage.
    • On the Treatments landing page, the File and Database tabs are empty, and you cannot open the templates.
    • The Segments landing page is empty.
  9. After you complete confidence testing, communicate your go/no-go decision to Pega Cloud services.
  • Previous topic Creating a Pega Customer Decision Hub test package for the go/no-go upgrade stage
  • Next topic Pega Customer Decision Hub 8.5 Feature Adoption for Pega Cloud Services Environments

Tags

Pega Customer Decision Hub 8.5 Decision Management

Have a question? Get answers now.

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

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

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