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

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.

To configure the data page to satisfy all the requirements in the scenario:

Create a thread-level data page with parameters that uses a connector as its source (Answer B):

Explanation: A thread-level data page ensures that the data is specific to the current user session and not shared across multiple sessions. Using parameters allows for flexibility in filtering and retrieving the required transactions. The connector source ensures data is fetched from the external service as needed.

Using Data Flows:

Leverage data flows to read and process data efficiently.

Utilize datasets to source the required data.

Option A:

Use a utility to post data to a queue processor.

The queue processor will then handle posting the data to the data warehouse over REST.

Option B:

Alternatively, the utility can synchronously post data directly to the data warehouse.

This ensures immediate transfer of data upon resolution of a case.

References:

Pega Platform Data Flow Documentation

Pega Academy Course on Integration and Data Synchronization