Using the decision table, you can find the label for a customer with a credit score of 240 and an average balance of 35000 by following these steps:

Start from the top row and check if the customer’s credit score is less than 150. If yes, then the label is Very Poor. If no, then move to the next row.

Check if the customer’s credit score is less than 175 and their average balance is less than 25000. If yes, then the label is Poor. If no, then move to the next row.

Check if the customer’s credit score is less than 200 and their average balance is less than 50000. If yes, then the label is Fair. If no, then move to the next row.

Check if the customer’s credit score is less than 250 and their average balance is less than 75000. If yes, then the label is Good. If no, then move to the last row.

The last row applies to all other cases that do not match any of the previous conditions. The label for this row is Very Poor.

In this case, the customer’s credit score is not less than 150, so the first row does not apply. The customer’s credit score is less than 175, but their average balance is not less than 25000, so the second row does not apply either. The customer’s credit score is not less than 200, so the third row does not apply. The customer’s credit score is less than 250 and their average balance is less than 75000, so the fourth row applies. Therefore, the label for this customer is Poor.

To implement this requirement, you need to configure a dynamic template in Customer Decision Hub. A dynamic template is a type of template that allows you to define a common action flow pattern for a group of actions that share similar characteristics, such as channel, issue, or group. You can specify which properties and components are required for each action in the group, and how they are mapped to the action flow template. This way, you can reuse the same action flow template for all the credit card actions, while still allowing some variations in their content and configuration. Verified References:  Pega Academy - Decisioning Consultant - Creating dynamic templates

The outbound run delivers 75 emails and 25 SMSes for the Standard card offer because the volume constraint is set to limit the number of actions per channel per day. The email channel has a limit of 75 actions per day, so all 75 email offers are delivered. The SMS channel has a limit of 25 actions per day, so only 25 SMS offers are delivered. The remaining 50 SMS offers are not delivered because they exceed the volume constraint.

According to the best practice, a single change request should be created in the 1:1 Operations Manager portal, because both changes are related to the engagement policies and propositions that are managed in this portal. The Pega Customer Decision Hub portal is used to design and test the decision strategies, not the engagement policies and propositions. Verified References:  Pega Decisioning Consultant | Pega Academy

The score calculation is independent of the strategy and no change is required. When you use a scorecard component in a decision strategy, you only need to specify the name of the scorecard rule and the output property that will store the score value. The scorecard rule itself defines how the score is calculated based on the input properties and factors. Therefore, if you update the scorecard rule to include a new property in the calculation, you do not need to make any changes in the decision strategy for the updated scorecard to take effect. Verified References: [Pega Academy - Decisioning Consultant - Using scorecards]

To implement this requirement, you need to select the Refresh the audience checkbox in the outbound run configuration. This option allows you to refresh the audience data before each run by executing a data flow that reads from your customer data source and updates your customer data set. This way, you can ensure that the outbound run always uses the latest customer information available in your system. Verified References:  Pega Academy - Decisioning Consultant - Configuring outbound runs