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

Ensuring that new team members adhere to best practices can be achieved through the following methods:

Branch Review: Utilize the branch review feature in Pega, where senior team members can review the contents of the branch. This allows experienced developers to provide feedback and ensure that the new rules meet the required standards.

Branch Quality Review: Regularly review the quality of the branch to identify any rules that have guardrail warnings. Guardrails are best practice guidelines in Pega, and addressing these warnings helps maintain high-quality, robust rules.

References: Pega Platform documentation on branch development and guardrail compliance.

 Engagement Policy Condition: This condition is used to specify the criteria that a customer must meet to be eligible for an offer, such as having an annual income above USD 150,000 for a Gold credit card.

 Implementation: In the Next-Best-Action Designer, configure the engagement policy to include an income threshold check to ensure only eligible customers receive the offer.

 Reference: Pega documentation outlines how to set up engagement policies to define conditions under which offers are presented (Pega Customer Decision Hub, Engagement Policies).

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.