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

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

The optimal solution to route the mortgage case to the specialist when the credit report is complete is to add a wait shape to the mortgage flow with a case dependency. This ensures that the mortgage flow advances to the next assignment only when the credit report case is resolved. This method is straightforward and leverages Pega's built-in case dependency management. References:

Pega Case Management: Case Management

 Situational Layer Cake™ Concept: This approach allows for different rules to be applied based on varying contexts like geography, business unit, or product line, without duplicating logic that remains consistent across layers.

 Base Layer for Common UI Rules: Placing the UI rules in the base layer ensures that common interface elements are shared across all divisions, promoting reusability and consistency.

 New Layer for Division-specific Rules: Creating a new layer for the payment rules specific to each division allows customization without affecting other parts of the application. This structure enables the organization to handle division-specific requirements (like different payment methods) efficiently.

 Reference: According to Pega’s best practices for layering, it is advised to place common elements in a shared layer and division-specific elements in their respective layers. This method optimizes rule inheritance and specialization (Pega Platform 8.7 Documentation, Layering and Class Structure).