Skip to main content

Using a scorecard for action-level suitability

Archived

3 Tasks

20 mins

 Visible to: All users
Beginner Pega Customer Decision Hub 8.5 English
This content is now archived and is no longer updated. Progress is not calculated. Pega Cloud instances are disabled, and badges are no longer awarded. Click here to continue your progress in 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 > = 400.

The credit score value is available in the data model, and 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 Analyst

CDHAnalyst

rules
Caution: To reuse the exercise system from a previous challenge, first complete the Using a scorecard for group-level suitability challenge. Otherwise, click Initialize Pega or Reset Instance in this challenge. 

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 > = 400.
The credit score value is present as a customer property, but it is not computed for every customer. You must use an existing scorecard rule, Determine Credit Score, which computes a customer’s credit score in case the score is not available.

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

 

Task 2: 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 3: Confirm your work

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

Customer

Credit Score

Results

Rewards Plus Card

Premier Rewards card

John

350

N

N

Arnold

400

Y

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

 

Note: Arnold is eligible for all four credit card offers. If you want to to see the effect of the changes for Arnold, you must disable both the Standard Card and Rewards Card offers, as these have higher priority. To disable an offer, in the Details section of the Offer landing page, mark the availablity as Never.
CH20726_1_Image _3.png

Challenge Walkthrough

Detailed Tasks

1 Create a new Suitability strategy to implement the Action-level Suitability criterion

  1. Log in as Decisioning Analyst with user name CDHAnalyst and password rules.
  2. In the navigation pane on the left, click Intelligence > Strategies.
  3. Click Credit Score to open the decision strategy.
  4. In the upper right, click Check out.
  5. On the canvas, click DetermineCreditScore, and then select Properties to open the scorecard component and enable the score calculation.
    1. Click the Score mapping tab.
    2. Select the Enable score mapping check box.
    3. Set the score to a strategy property CreditScore.
      Score mapping
    4. Click Submit. Now you have the credit score from the Scorecard component, but this should only be used if the CreditScore property is not set.
  6. On the canvas, right-click and select Enrichment > Set property to add the component.
    Adding set property
    1. Right-click the Set property component, and then select Properties to set the CreditScore.
    2. In the Name field, enter Final Credit Score.
    3. Click Add item.
    4. In the Action list, select Set.
    5. In the Target field, enter or select .CreditScore.
    6. Open the Expression builder to define the condition as if(PropertyHasValue(Customer.CreditScore), Customer.CreditScore, .CreditScore)
      Note: Set the CreditScore to either the available CreditScore value from the customer data data model or the value computed by the scorecard.
    7. Click Submit.
      Adding target
  7. Open the Filter component properties to modify the filter condition.
  8. Open the Expression builder to define the condition as FinalCreditScore.CreditScore>=300. A blue dotted line is added to the canvas that connects the Filter and Set property components.
  9. Connect the Scorecard Model component to the Set property component.
    Strategy
 
  1. On the canvas, right-click, and then select Arbitration > Filter to add the component.
  2. Right-click the Filter component, and then select Properties to enter the following information:
    1. In the Name field, enter Credit Score >= 400.
    2. Open the Expression builder to define the condition as FinalCreditScore.CreditScore>=400
    3. Click Submit.
  3. Connect the External Input to the Filter component.
  4. Connect the Filter component to the Results.
    Final strategy
  5. Click Check in to complete your strategy modifications.
  6. On the canvas, select the Set Property component and enter the following information to test the strategy:
    Testing john DT
    1. Data transform: John
    2. For external inputs use strategy: RewardsPlusAndPremier
    3. Click Save & Run to verify the results of the scorecard
      Test result
 
  1. On the canvas, click Filter (Credit Score > = 400) and notice that the strategy does not output any results.
    Testing john DT
  2. Repeat steps 15 and 16 and check the results for the Arnold data transform.
    Result for John
  3. On the canvas, click Filter (Credit Score > = 400); notice that Arnold is suitable for both the Rewards Plus and Premier Rewards card offers.
    John result

2 Define the Engagement Policy with the newly created strategy

  1. In Customer Decision Hub, in the navigation pane on the left, click Next-Best-Action > Designer.
  2. In Next-Best-Action Designer click Engagement policy to access the engagement policies.
  3. In the Business structure, click the CreditCards group.
  4. Click Edit.
  5. In the Offers section, click the Rewards Plus card to define the action-level suitability condition.
  6. Click Engagement policy.
  7. Click Check out.
  8. In the Suitability section of the engagement policy, delete the existing action-level suitability rule for the Rewards Plus card. 
  9. In the first drop-down list, click the down arrow.
  10. In the list, select the Strategy > Credit Score.
  11. Ensure that has results and for Credit Score >= 400 are selected.
    Action level suitability
  12. Click Check in to save the action-level suitability rule.
  13. and then close.
  14. Repeat steps 5-13 for the Premier Rewards card.
  15. Click Save.

 

3 Confirm your work

  1. On the Exercise System landing page, click on U+ Bank to open the website.
    CH20726_13_Image _0.png
  2. On the website main page, in the upper right, click Log in to log in as a customer.
  3. Log in as John, and then verify that he is not suitable for the Rewards Plus or Premier Rewards card offers.
  4. Optional: Check the results for Arnold.
Note:

Arnold is eligible for all four credit card offers. If you want to to see the effect of the changes for Arnold, you need to disable both the Standard Card and Rewards Card offers, as these have a higher priority. To disable an offer, in the Details section of the Offer landing page, mark its availability as Never.

If you test for Arnold, be sure to re-enable the two offers after.

CH20726_14_Image .png

 

Available in the following mission:

Return to mission Continue mission

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