Skip to main content

Running Pega Customer Decision Hub setup wizard

4 Tasks

45 mins

Visible to all users
Intermediate Pega Customer Decision Hub 8.8 Next Best Action Decision Management System Administration English

Scenario

U+ Bank has decided to improve the experience of its customers with personalized decisions that predictive and adaptive analytic models drive. To start development, the project team wants to set up the application by running the Pega Customer Decision Hub™ setup wizard. As the system administrator, create a new operator with the right access group to launch the setup wizard and configure the application that uses the financial services data model and Next Best Action designer template.

Use the following credentials to log in to the exercise system:

Role User name Password
System administrator SystemAdmin rules

Your assignment consists of the following tasks:

Task 1: Create SystemArchitect operator

Log in to Dev Studio as the system administrator to create a new System Architect operator with the following details:

Field Value

Operator ID

SystemArchitect

Access Group

CDHTemplate:CDHAdmins

Organization

pega.com

Division

Administration

Unit

Installation

Login password

rules

Task 2: Set up Customer Decision Hub

Log in to App Studio as the System Architect, and then, in Dev Studio, use the New Application wizard to initiate the Customer Decision Hub setup wizard.

To create the Customer Decision Hub application, use the following details:

Field Value

Application Name

CDH

Organization Name

UBank

Industry Name

Retail banking

Repository

CDHData

Task 3: Explore the context dictionary

Log in to App Studio, and then explore the context dictionary and repository settings.

Task 4: Explore the applications

Log in to Dev Studio, and then explore the generated applications and other artifacts that the wizard sets up.

 

You must initiate your own Pega instance to complete this Challenge.

Initialization may take up to 5 minutes so please be patient.

Challenge Walkthrough

Detailed Tasks

1 Create SystemArchitect operator

  1. On the exercise system landing page, click Pega CRM suite to log in to Dev Studio.
  2. Log in to Dev Studio as the system administrator:
    1. In the User name field, enter SystemAdmin
    2. In the Password field, enter rules.
  3. In the header of Dev Studio, click Create > Organization > Operator ID to create a new operator.
    Creating a new operator id
    1. In the Operator ID short description text box, enter System Architect.
    2. In the Operator ID field, enter SystemArchitect.
      Creating the system architect
    3. In the upper-right corner, click Create and open to edit the Operator ID record.
  4. On the Operator ID record, on the Profile tab, in the Application Access section, in the Access Group field, enter or select CDHTemplate:CDHAdmins.
    Adding CDHTemplate CDH Admin access group
    Caution: Ensure that the default access group radio button is selected.
  1. Click the Work tab to update the organizational unit.
  2. On the Work tab, in the Routing section, click Update to open the Update Organizational Unit dialog box.
    Update the org unit
  3. In the Update Organizational Unit dialog box, complete the following steps:
    1. In the Organization field, enter or select pega.com.
    2. In the Division field, enter or select Administration.
    3. In the Unit field, enter or select Installation.
    4. Click Submit to close the Update Organizational Unit dialog box.
      Configure the organization unit
  4. On the operator ID record, click the Security tab to update the login credentials.
  5. On the Security tab, select the Allow rule check out checkbox.
    Allow rule checkout
  6. Click Update password to update the login password for the System Architect operator:
    1. In the Change Operator ID Password dialog box, in the New password enter rules.
    2. In the Confirm new password field, enter rules, and then click Submit.
      Entering rules for password
  7. In the upper-right corner of the operator ID record, click Save.
  8. In the lower-left corner, click the user icon, and then select Log off to log out of Dev Studio.

2 Set up Customer Decision Hub

  1. Log in to App Studio as the setup operator:
    1. In the User name field, enter SystemArchitect.
    2. In the Password field, enter rules.
  2. In the upper-right corner, close the Welcome to Customer Decision Hub window.
    Welcome to Customer decision hub
  3. In the header of App Studio, click App Studio > Dev Studio to switch workspaces.
    Switching to dev studio
  4. In the header of Dev Studio, click Application: Pega Customer Decision Hub > New Application.
  5. On the New Application tab, select Pega Customer Decision Hub, and then click Continue.
    Select Pega Customer Decision Hub
  6. On the What type of application do you want to build? page, select Build with Pega Customer Decision Hub.
    Build with Pega Customer Decision Hub
  7. On the Build using Customer Decision Hub Setup Wizard page, click Launch CDH Setup Wizard to launch the setup wizard.
    Launch CDH Setup Wizard
  8. In the lower-right corner, click Next to begin the setup process.
    Welcome to Customer Decision Hub
  9. Complete the Define the application and organization name step:
    1. In the Organization Name field, enter UBank.
    2. In the Application Name field, enter CDH.
      Enter org name and app name
  10. In the Choose your industry step, click Retail banking, and then click Next.
    Select retail banking
  11. In the Choose your repository step, in the Select a repository list, select CDHData, and then click Next.
    Select CDH data repository
    Note: The CDHData is a preconfigured AWS S3 repository for the exercise. In Pega Cloud® services, you have Pega Cloud File Storage preconfigured for you as a default repository. You can select this repository or a different one as your decision repository. Users can later set up the repository on client-cloud and on-premise installations or select a repository if one already exists. The system administrator can configure the repository in Dev Studio by selecting Create > SysAdmin > Repository.
  1. On the Review your configuration step, click Start.
    Review your configuration
    Caution: This process might take up to 30 minutes. During this time, the setup wizard creates new applications, applies the financial data model, generates the context dictionary, applies the Next-Best-Action Designer template, and creates data flows to export interaction data.
  1. When the setup is complete, click Open Customer Decision Hub to log in to App Studio.
    Setup is complete
    Caution: The setup wizard automatically updates the operator ID record of the System Architect with the CDH:CDHAdmins access group.

3 Explore the context dictionary

  1. In the upper-right corner, close the Welcome window.
  2. In the navigation pane of App Studio, click Settings > Context Dictionary to review the context entities.
  3. On the Context Dictionary landing page, in the PRIMARY CONTEXT section, click the Gear icon to review the settings of the customer context.
    Verify the customer context
    Note: The setup wizard uses the organization name and enterprise application name to build the primary context as UBank-CDH-Data-Customer and assigns required attributes.
  1. On the right, in the Context pane, review the Associated data section.
    Review the Account context
    Note: The setup wizard creates a new page list property, .Accounts, and builds the association with the account class by using an AccountsJoin association.
  1. On the Context Dictionary landing page, in the Account section, click the Gear icon to review the settings of the account context.
    Verify the account context
  2. In the navigation pane of App Studio, select Settings > General to review the general settings.
  3. On the General landing page, click the Data tab, to review the Data import settings.
    Review the data import settings
    Note: The system uses the Data import settings when it defines the data jobs to ingest data into Customer Decision Hub.
  1. On the General page, on the Data tab, click Data export to confirm that the value of the Repository field is CDHData.
    Review the data export settings

4 Explore the generated applications

  1. In the header of App Studio, click App Studio > Dev Studio to switch workspaces.
    Switch to Dev Studio
  2. In the header of Dev Studio, click Application: CDH > Definition to explore the application record.
    Review the Application Definition
  3. On the Definition tab, review the following information:
    1. In the Built on applications section, verify that the Customer Decision Hub implementation application uses PegaMarketing_FW as the built-on application.
      Review Built on applications
    2. In the Enabled components section, verify that the value in the Component field is FinancialServicesXCARDataModel.
      Review enabled components
    3. In the Application rulesets section, verify that the rulesets are in place.
      Review application rulesets
      Note: The system automatically adds the OLSTDRCDH:01-01-01 ruleset to the ruleset stack to support change management and store artifacts from the Business Operations Environment (BOE) of Pega 1:1 Operations Manager™.
  1. In the navigation pane of Dev Studio, click Records > Application Definition > Application to review the application records.
  2. Confirm that there are three new applications along with Customer Decision Hub:
    • CDH standard release
    • CDH fast release
    • 1:1 Operations manager Ext (CDH)
    Review the application list
    Caution:
    CDH standard release (OLSTDRCDH) is the overlay application in which the content team manages day-to-day activities such as creating, updating, and deleting new actions and treatments. Use this application in the BOE environment only. Do NOT use the application in the development environment. 1:1 Operations Manager application is created to prepare and support change management when the BOE environment is ready.
    CDH fast release (OLFRCDH) is another overlay application in which the content team manages emergency fixes that apply to Production on an ad-hoc basis. Use this application in the BOE environment only. Do NOT use the application in the development environment. This application contains a separate branch ruleset and then uses the OLSTDRCDH application to support the fast-release emergency deployments.
    1:1 Operations Manager Extension (OpsExtCDH) is the application in which the project team can extend and customize the user experience of 1:1 Operations Manager, such as customizing the approval processes and adding or removing new properties to screens.
    Customer Decision Hub (CDH) is the enterprise application in which the project team and enterprise capabilities teams work to develop the foundation of Customer Decision Hub and extend integration points with new channels.
  1. In the navigation pane of Dev Studio, click Configure > Decisioning > Decisions > Data Flows > Real-time Processing to review the real-time data flow list.
    Open the real-time data flows
  2. On the Real-time processing tab, verify that the system generated the WriteDataToDecisionFiles and WriteDataToInteractionFiles data flows.
    Review the real-time data flows
    Caution: The WriteDataToDecisionFiles data flow writes every Customer Decision Hub decision to the Amazon S3 repository for auditing purposes. The WriteDataToInteractionFiles data flow writes every interaction history record that Customer Decision Hub captures to the Amazon S3 repository.
    In a real-life scenario, the WriteDataToDecisionFiles data flow is inactive by default. You can activate this data flow by setting the decision/writeToStream dynamic system setting to true. In the exercise system, the dynamic system setting of decision/writeToStream is true.
  1. In the header of Dev Studio, click Launch portal > Customer Decision Hub to launch the Customer Decision Hub portal.
  2. In the navigation pane of Customer Decision Hub, click Next-Best-Action > Designer to open Next-Best-Action Designer.
  3. Review the Next-Best-Action Designer settings for each tile:
    1. Click Taxonomy to review the business structure in Next-Best-Action Designer.
      Review the taxonomy
    2. Click Constraints to review the predefined contact policy library.
      Review the Constraints tab
    3. Click Engagement policy to review available engagement policies.
      Review the engagement policies
    4. Click Arbitration to verify the prioritization algorithm.
      Review the arbitration tab
    5. Click Channels tab to review available channels, real-time, and event-driven containers.
      Review the channel tab

This Challenge is to practice what you learned in the following Module:


Available in the following mission:

If you are having problems with your training, please review the Pega Academy Support FAQs.

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 Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice