Skip to main content

Using a scorecard for action-level suitability

3 Tasks

25 mins

 Visible to: All users
Beginner
Pega Customer Decision Hub 8.8
English
Verify the version tags to ensure you are consuming the intended content or, complete the latest version.

Scenario

U+ Bank is cross-selling on the web by showing various credit cards to its customers. Due to the credit limits of each card, the business wants to include an additional suitability criterion:

  • Rewards Plus and Premier Rewards are suitable only if Credit score > = 700.

The credit score value is available in the data model. An external process populates the value in a nightly batch. However, the credit score is not computed for every customer.

As a result, the business already implemented a scorecard rule, Determine Credit Score, which computes the credit score of a customer in case the score is not available.

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

Role User name Password
Decisioning Architect DecisioningArchitect rules

Your assignment consists of the following tasks:

Task 1: Create a new suitability strategy to implement the action-level suitability criterion

Rewards Plus and Premier Rewards are suitable only if Credit score > = 700.

The credit score value is present as a customer property. But it is not computed for every customer. Use an existing scorecard rule, Determine Credit Score, which computes a customer's credit score if the score is unavailable.

Note: You can use the Credit Score decision strategy as a starting point for the new strategy, which imports the correct scorecard.
Caution: To check if a customer property is set, you can use the PropertyHasValue() function.

Task 2: Test the decision strategy

Test the decision strategy to see that Barbara is suitable for getting the credit card and Robert is not suitable for getting the credit card.

Task 3: Define the engagement policy with the newly created strategy

Define the engagement policy with the newly created strategy as an action-level suitability rule.

Task 4: Confirm your work

Log in to the U+ Bank website as Barbara and Robert and verify the offers.
Use the information in the following table for verification.

Customer

Credit Score

Results

Rewards Plus Card

Premier Rewards card

Barbara

750

Y

Y

Robert

550

N

N
Note: When testing the strategy, use the RewardsPlusAndPremier strategy for external inputs. This strategy outputs both the Rewards Plus and Premier Rewards actions.

 

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 a new suitability strategy to implement the action-level suitability criterion

  1. On the exercise system landing page, click Pega CRM suite to log in to Pega Customer Decision Hub™.
  2. Log in as a decisioning architect:
    1. In the User name field, enter DecisioningArchitect.
    2. In the Password field, enter rules.
  3. In the navigation pane of Customer Decision Hub, click Intelligence > Strategies to open the Strategies landing page.
  4. On the Strategies landing page, double click Credit Score to open the decision strategy.
  5. In the upper right, click Check out to edit the Credit Score strategy.
  6. On the canvas, right-click the DetermineCreditScore component, and then select Properties to enable the score calculation.
    1. In the Scorecard model properties dialog box, click the Score mapping tab.
    2. Select the Enable score mapping checkbox.
    3. In the mapping field, enter or select .CreditScore.
      score mapping
    4. Click Submit to close the dialog box.
      Note: Only use the Credit Score decision strategy if the CreditScore property is not set.
  1. On the canvas, right-click, and then select Enrichment > Set property to add the component.
  2. Right-click the Set Property component, and then select Properties to set the CreditScore.
    1. In the Set property properties dialog box, in the Name field, enter Final Credit Score.
    2. In the Define action, target, and source section, click Add item to add an action.
    3. In the Action list, select Set.
    4. In the Target field, enter or select .CreditScore.
    5. Next to the Source field, click the Open icon to open the Expression builder to define the condition.
    6. In the Expression builder, enter if(PropertyHasValue(Customer.CreditScore), Customer.CreditScore, .CreditScore), and then click Submit.
      Note: Set the CreditScore to either the CreditScore value that is available from the data model of the customer data or the value that the scorecard computes.
    7. Click Submit to close the Set property properties dialog box.
      set property properties
  1. On the canvas, right-click the Filter component, and then select Properties to modify the filter condition.
    1. In the Filter properties dialog box, next to the Filter Condition field, click the Open icon to open the Expression builder to define the condition.
    2. In the Expression builder, enter FinalCreditScore.CreditScore>=600, and then click Submit.

A blue dotted line is displayed on the canvas that connects the Filter and Set property components. The existing Filter condition change is required to make it compatible with the Set property component introduced in step 7.

  1. On the canvas, hover over the Scorecard Model component, and then click and drag the arrow to connect it to the Set property component.
    strategy before
  2. On the canvas, right-click, and then select Arbitration > Filter to add the component.
  3. Right-click the Filter component, and then select Properties to modify the filter.
    1. In the Filter properties dialog box, in the Name field, enter Credit Score >= 700.
    2. Next to the Filter Condition field, click the Open icon to the Expression builder to define the condition.
    3. In the Expression builder enter FinalCreditScore.CreditScore>=700, and then click Submit.
    4. Click Submit.
  4. On the canvas, hover over the External Input shape, and then click and drag the arrow to connect it to the Filter component.
  5. Repeat step 13 to connect the Filter component to the Results shape.
    strategy after
  6. In the header of the strategy, click Check in to complete your strategy modifications.
  7. Enter the check-in comment, and then click Check in.

2 Test the decision strategy

  1. On the right, expand the Test run pane.
  2. Expand Settings.
  3. On the canvas, select the Set Property component, and then, in the Test run pane, enter the following information to test the strategy:
    1. Data transform: Barbara
    2. For external inputs use strategy: RewardsPlusandPremiumRewards
      run
    3. Click Run to verify the results of the scorecard.
  1. On the canvas, click Filter (Credit Score > = 700), and then, in the Test run pane, confirm that Barbara is suitable for both the Rewards Plus and Premier Rewards card offers.
    cards eligible for Barbara
  2. Repeat steps 2 and 3 and check the results for the Robert data transform.
    test result for robert
  3. On the canvas, click Filter (Credit Score > = 700), and then, in the Test run pane, confirm that Robert is not suitable for both the Rewards Plus and Premier Rewards card offers.
    cards eligible for robert
  4. In the header of the strategy, click Actions > Mark as relevant record.
    Note: In case you are using the instance from the previous challenge, steps 7 to 11 are not necessary.
  1. In the Mark as relevant record success banner, click View to launch the Application: Inventory page.
    open relevant records
  2. On the Application: Inventory page, next to the Credit Score strategy, click the More icon, and then select Associate to categories to open the Associate categories dialog box.
    associate categories
  3. In the Associated categories list, select Suitability, and then click OK.
    associate suitability
  4. Close the Application: Inventory page.
    Note: Close the Strategy page.
    Click OK if you see the Unsaved changes window.

3 Define the engagement policy with the newly created strategy

  1. In the navigation pane of Customer Decision Hub, click Next-Best-Action > Designer to open Next-Best-Action Designer.
  2. In Next-Best-Action Designer, click Engagement policy to access the engagement policies.
  3. In the Business structure pane, in the Grow section, click Credit cards to open the group.
  4. Click Edit to modify the group.
  5. Expand the Customer actions section.
  6. In the Actions area, click the Rewards Plus card to define the action-level suitability condition.
  7. Click the Engagement policy tab.
  8. Click Check out.
  9. In the Suitability section of the engagement policy, click the Add icon to add the suitability rule:
    1. In the first list, ensure that Customer is selected.
    2. In the second list, select the Strategy > Credit Score.
      Note: If the strategy is not displayed, log out of Pega Customer Decision Hub, and then log back in.
    3. Ensure that has results for Credit Score >= 700 is selected.
      SUITABILITY FOR ACTION
  1. Click Check in to save the action-level suitability rule.
  2. Enter check-in comments, and then click Check in.
  3. Close the action.
  4. Repeat steps 6 through 12 for the Premier Rewards card.
  5. Click Save.

Confirm your work

  1. On the exercise system landing page, click U+ Bank to open the website.
    U Bank
  2. On the main page of the website, in the upper right, click Log in to log in as a customer.
  3. Log in as Barbara, and then verify that she is suitable for a credit card.
  4. Log out.
  5. Log in as Robert, and then verify that he is not suitable for credit card offers.

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

Available in the following mission:

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

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 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