PEGAPCDC87V1 Exam Dumps : Certified Pega Decisioning Consultant (PCDC) 87V1

 Requirement for Total Revenue Calculation:

MyCo needs to calculate the total revenue of three new actions over a specified period.

The goal is to aggregate the revenue generated by these actions.

 Use of Group By Component:

The Group By component is used to aggregate data based on specified properties.

In this scenario, it can be configured to sum the revenue of the three new actions.

 Configuration Steps:

Configure a single Group By component to group the actions by their identifiers.

Use the aggregation function within the Group By component to calculate the sum of the revenue for the grouped actions.

 Efficiency and Simplicity:

Using a single Group By component simplifies the strategy by avoiding redundancy.

It ensures that all actions are considered in a single aggregation process, providing an accurate total revenue calculation.

 Verification from Pega Documentation:

According to Pega's guidelines, a single Group By component can efficiently compute total values such as revenue by grouping and aggregating data.

Paul cannot see the Reward card offer due to the contact policies defined by U+ Bank:

Contact Policies Defined:

Policy 1: Suppress a group of credit card offers for 30 days if any credit card offer is rejected three times in any channel in the past 15 days.

Policy 2: Suppress the Reward card offer for 7 days if it is rejected twice in any channel in the last 7 days.

Paul’s Rejection History:

Paul has rejected other credit card offers twice on the web channel and once in the contact center within the last 15 days.

Reason for Suppression:

Due to Policy 1, since Paul has rejected any credit card offer (not specifically the Reward card) three times in any channel in the past 15 days, all credit card offers, including the Reward card offer, are suppressed for 30 days.

Understanding the Suppression Logic:

Step 1: The decision strategy evaluates the rejection history of offers.

Step 2: It applies the contact policies to determine which offers should be suppressed.

Step 3: In this case, the policy conditions are met due to multiple rejections of credit card offers, leading to the suppression of the Reward card offer.

References:

Pega-Customer-Decision-Hub-User-Guide-85.pdf: "Setting constraints, contact policy limits, and controls" section.

Pega documentation on "Managing contact policies".

 Understanding the Scenario Planner Output:

The image shows the projected reach and projected responses for several credit card offers, including the Standard card.

The "Projected responses" column indicates the number of customers expected to respond positively to each offer.

 Interpreting the Data for the Standard Card:

For the Standard card, the "Projected responses" is 21, with a change indicator showing a decrease of 7.

This decrease is factored into the projected response, meaning the expected number of positive responses after considering the applied business weight.

 Step-by-Step Calculation:

The base projected responses for the Standard card is 21.

The decrease of 7 has already been factored into this projection.

Therefore, the number of customers likely to accept the Standard card remains 21, as it represents the final projected response after adjustments.

 Verification from Pega Documentation:

The Scenario Planner in Pega Customer Decision Hub provides these projections to help visualize the impact of business weight adjustments and other lever changes on customer actions.