PEGACPLSA88V1 Exam Dumps - Certified Pega Lead System Architect (CPLSA) Exam 8.8

To change the threshold value for the USD2000 credit limit from <175 to <200 in Pega Customer Decision Hub:

Locate the Scorecard Model:

Navigate to the scorecard model that calculates the customer credit score.

Modify the Cutoff Value:

Go to the Results tab of the scorecard model.

Find the condition for the USD2000 credit limit which is currently set to .pxSegment <= 175.

Change this condition to .pxSegment <= 200.

Save and Validate:

Save the changes in the scorecard model.

Validate the scorecard model to ensure it reflects the new threshold.

This approach directly modifies the threshold within the scorecard model's configuration.

References: Pega Customer Decision Hub Implementation Guide

To address difficulty in creating a customer service request through Facebook Messenger:

Change the text analyzer configured for the channel (Answer C):

Explanation: The text analyzer is responsible for interpreting user input. Improving its configuration can enhance its ability to understand and process customer requests more accurately.

Summarize Function with Filter Condition After Aggregation:

Using a report with a summarize function on Quantity and a filter condition applied after aggregation ensures that the report accurately displays categories with more than 5 items ordered.

References:

Pega documentation on report definitions and aggregation functions outlines how to apply filters after summarizing data to meet reporting requirements.

Therefore, the correct answer is:

C. A report with a summarize function on Quantity and filter condition Sum (Quantity) > 5 that the system applies after aggregation.

ï‚· Increasing Stage Upweighting: This technique involves gradually increasing the priority or weight of offers in a specific stage of the customer journey, promoting active engagement and progression through the journey stages.

ï‚· Second Stage: In the second stage, which presents available offers, enabling increasing stage upweighting ensures that offers are promoted more actively over time, enhancing visibility and uptake.

ï‚· Reference: Pega's customer journey framework and decision strategies documentation detail how to use stage upweighting to optimize customer engagement and offer promotion (Pega Customer Decision Hub, Customer Journey and Engagement Strategies).

To avoid creating unnecessary case-related properties and views:

Work Pool Level Definitions: Define most properties and sections at the work pool level to ensure they are reusable across multiple case types. This approach reduces redundancy and simplifies maintenance.

Data Types: Create data types that correspond to the case type when necessary. This helps in organizing related data and promotes reuse.

Data Reference Field Type: Use the data reference field type in the case type's data model tab. This allows you to link to existing data types without duplicating properties, maintaining data integrity and reducing redundancy.

References: Pega Platform documentation on data modeling, work pools, and data reference field types.

Custom Split-for-Each Process Step:

In the case designer, add a new step in the Processing stage where you need to create child cases.

Select the "More" option and then "Split for Each".

Configure the split to create a separate child case for each item in the page list property.

Configure Data Propagation:

Ensure that data from the parent case is propagated to each child case.

In the case designer, go to the data propagation settings and map the relevant properties from the parent case to the child cases.

Use Page List Property:

Create a page list property in the parent case to store the list of suspected fraudulent charges.

Configure the case type to iterate over this page list property when creating child cases.

References:

Pega Academy: Implementing Case Management.

Pega Documentation: Split-For-Each and Data Propagation.

To configure the application to handle the requirement where employees can designate alternate operators to perform their work while they are on vacation, follow these steps:

Define a custom Access When rule:

Create an Access When rule named pxAssignedToMeOrAlternate. This rule will allow the system to check whether the assignment is for the current user or their designated alternate.

The rule should include logic to determine if the assignment belongs to the operator or the operator’s alternate.

Modify the pyUserWorkList Report Definition:

Access the pyUserWorkList report definition which is used to display the worklist for the current user.

Modify this report to include a filter condition using the pxAssignedToMeOrAlternate Access When rule. This ensures that the report displays assignments for both the current user and any assignments for which they are an alternate.

Assign Worklist assignments to alternate operators:

Ensure that the assignments visibility is adjusted accordingly by modifying the security settings to allow access to assignments for alternate operators.

Testing and Verification:

Test the configuration to ensure that alternate operators can see and access the worklist items of the operators they are covering for.

This approach leverages Pega’s Access When rules to dynamically adjust the visibility of assignments based on operator relationships, ensuring that alternate operators can perform work as needed without requiring manual assignment transfers.

References:

Pega Documentation on Access When rules: Access When Rules

Pega Documentation on Report Definitions: Report Definitions

A rule-utility-function (RUF) has the advantage of being directly callable from a decision table, which is a common requirement in Pega applications for implementing business logic. This direct invocation capability simplifies the design and execution of decision rules. References:

Pega Rule-Utility-Functions: Rule-Utility-Functions