Skip to main content


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

Prerequisites for Pega Customer Decision Hub

Updated on May 30, 2022

Before you start your Pega Customer Decision Hub implementation, complete the prerequisite tasks, specific to your deployment type.

Deployment in Pega Cloud

  1. Optional: Complete the "Discover" phase of the Inbound for Digital Channels Microjourney.

    The Discover section in the MLP Backlog: Cross/Upsell – Digital book outlines the initial tasks required to successfully implement Pega Customer Decision Hub.

  2. Verify access to the cloud environment.

    For more information, see Pega Cloud Services.

  3. Determine which repository you want to use to export interactions and decisions.
  4. Determine which setup option in the Pega Customer Decision Hub setup wizard you want to use:
    Communications
    Recommended for telephone companies and communication service providers.
    Financial Services
    Recommended for banks and financial institutions.
    Other
    Recommended for companies in other industries, such as healthcare and insurance.

    For more information, see Pega Customer Decision Hub Product Overview

  5. From the system architect, obtain the credentials for a system architect operator in the CDHTemplate:CDHInstall access group. You need this operator to run the Pega Customer Decision Hub setup wizard in the development environment and create the implementation application.

Deployment on the premises and client-managed cloud

  1. Optional: Complete the "Discover" phase of the Inbound for Digital Channels Microjourney.

    The Discover section in the MLP Backlog: Cross/Upsell – Digital book outlines the initial tasks required to successfully implement Pega Customer Decision Hub.

  2. Set up your environments:
    • Development (SOR)
    • Staging
    • Business Operations Environment (BOE)
    • Production
  3. Install Pega Customer Decision Hub.

    For more information, see Pega Customer Decision Hub Installation Guide.

  4. From the system architect, obtain the credentials for a system architect operator in the CDHTemplate:CDHInstall access group. You need this operator to run the Pega Customer Decision Hub setup wizard in the development environment and create the implementation application.
  5. If a decision repository was not added during installation, add a repository to your system for exporting interactions and decisions from Pega Customer Decision Hub.

    For more information, see Creating a repository.

  6. Choose the organization name to use for naming rules in your application.
  7. Determine which setup option in the Pega Customer Decision Hub setup wizard you want to use:
    Communications
    Recommended for telephone companies and communication service providers.
    Financial Services
    Recommended for banks and financial institutions.
    Other
    Recommended for companies in other industries, such as healthcare and insurance.

    For more information, see Pega Customer Decision Hub Product Overview

  8. Obtain access to the Development environment.
  9. Enable decisioning nodes.

    For more information, see Enabling decision management services.

  10. Optional: By default, your application is created with the name CDH. If you want the application to have a different name, edit the MKTApplicationName dynamic system setting.

What to do next

Configure your Pega Customer Decision Hub application in the Development environment. For more information, see Configuring the Development environment.

  • Previous topic Introducing Pega Customer Decision Hub implementation
  • Next topic Configuring the Development environment

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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