Free Practice Questions for Pegasystems PEGACPLSA88V1 Exam

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 response data transform to satisfy all the requirements in the scenario:

Configure the data transform to copy only the first 10 matching records to a page list property (Answer A):

Explanation: This approach ensures that only the required number of transactions (10) are displayed initially, meeting the requirement of showing the most recent transactions without overwhelming the case worker with too much data.

To use customer properties like income and age in a Filter component:

Direct Access:

Customer properties such as income and age are directly available for use in decisioning components.

There's no need for additional components to enable access.

Using the Filter Component:

Simply drag and drop the Filter component into the decision strategy.

Use the customer properties directly in the filter logic (e.g., Customer.Income > 50000).

This is because Pega Customer Decision Hub typically provides direct access to commonly used customer properties.

References: Pega Decision Strategy Documentation

Create Access When Rule:

Go to Records Explorer > Security > Access When.

Create a new Access When rule that checks if the current user is either the primary or secondary owner of the account. Use conditions like current user = primary owner or current user = secondary owner.

Configure the Access When Rule:

Open the Account case type.

Go to the Security tab and in the Case Type rules, apply the created Access When rule to ensure that only users who meet the conditions (primary or secondary owners) can view or update the case.

Apply Access Control:

In the Access Role configuration, apply the Access When rule for read and write instances of the Account class.

Ensure that the roles assigned to the users have the necessary permissions configured.

Testing and Validation:

Test the implementation by logging in with users who are primary or secondary owners and verifying access.

Try logging in with users who are not owners to ensure access is denied.

References:

Pega Academy: Security and Access Control.

Pega Documentation: Access Control Policies and Access When Rules.

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 satisfy requirements using Skin rule customizations:

In the Skin rule, configure the importance field for each column included in a repeating layout (Answer A):

Explanation: Setting the importance field helps manage how columns are displayed on different devices, ensuring a responsive design.

When deciding between using a Wait shape or an assignment with an SLA in a Pega case flow:

Assignment with SLA (C):

An assignment with an SLA is preferred when there is a requirement to adjust the case urgency at the time of assignment creation. SLAs allow you to specify goals, deadlines, and escalation actions that can modify the urgency of the case.

This approach is suitable when you need to ensure that the case is handled within a certain timeframe and that the urgency can dynamically change based on business rules.

References:

Pega Case Management Best Practices

Pega SLA Configuration Guide

Enable Auditing:

On the Rule-Declare-Decision Table RuleForm, check the option to enable auditing.

Monitor Changes:

This configuration will track changes made to the decision table in the production environment.

To configure a report definition that lists new customer cases created in a given day and the average opening balance for all account child cases for each customer, you should use the "class join" feature in Pega. This feature allows you to join data from different classes, which is essential when dealing with cases and their child cases. Specifically, you can create a join between the customer case class and the account child case class to aggregate the average opening balance.