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

To troubleshoot a chronic performance issue in a cloud-based production application:

Review Performance Alerts and Exceptions in PDC (A): Pega Predictive Diagnostic Cloud (PDC) monitors and reports on the health and performance of Pega applications in real-time. Reviewing alerts and exceptions here can provide insights into the root causes of performance issues.

Review Performance Alerts and Exceptions in AES (D): Pega Autonomic Event Services (AES) also monitors system health and performance. It can help identify patterns and issues that occur during specific time frames.

References:

Pega PDC: Understanding Pega Predictive Diagnostic Cloud

Pega AES: Pega Autonomic Event Services Overview

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

To configure a process where three physicians can independently perform evaluations and ensure that only two evaluations are necessary to advance the case to the medical director, you should use the "Some" join condition in Pega.

Understanding Join Conditions in Pega:Pega provides various join conditions to handle subprocesses. The join conditions include "Any," "Some," and "All." These conditions dictate how and when the main process can proceed based on the completion of subprocesses.

Some Join Condition:The "Some" join condition allows the main process to advance once a specified number of subprocesses have been completed successfully. In this scenario, since only two out of the three physicians need to complete their evaluations for the case to move forward, the "Some" join condition is appropriate.

Configuration Steps:

Step 1: Define the subprocesses for the physicians' evaluations.

Step 2: Use the "Split For Each" shape to create multiple subprocesses.

Step 3: Configure the "Some" join condition and set the number of required completions to 2.

Step 4: Ensure that the main process waits for two evaluations before moving to the medical director review.

References:Pega Documentation on Join Conditions provides detailed steps and examples for configuring different join conditions, including the "Some" join condition.