Pegasystems PEGACPLSA88V1 - Certified Pega Lead System Architect (CPLSA) Exam 8.8

Identifying the Error Flow:

When stages are altered in a case type, in-flight cases can encounter issues if they try to advance to a now-missing stage.

pzStageProblems Flow:

This flow is initiated when there are problems advancing stages due to missing or reconfigured stages.

It helps to manage and resolve issues related to stage progression.

References:

Pega Platform Case Management Documentation

Pega Academy Course on Advanced Case Design

Team A publishes branch,

Automation server merges three branch,

Team B and C rebase the application

Test for Completeness:

Ensure that all possible conditions and outcomes are covered in the decision rule. This involves checking that there are no missing branches or conditions that could result in an undefined outcome.

Unit Testing:

Conduct unit tests to verify that all scenarios return the expected results. This helps in identifying any gaps or missing conditions in the rule.

References:

Pega Academy: Decision Rules and Validation.

Pega Documentation: Testing and Debugging Decision Rules.

Configure Activity for Background Execution:

Set the activity to execute in the background to prevent user interface delays.

Activity Setup:

Configure an activity that handles the connector call.

Declare Trigger:

Set up a declare trigger that activates when the case status changes to ensure the connector runs at the appropriate time.

To design a reporting strategy that displays the number of cases by status at the end of each month for a 12-month period, follow these steps:

Configure an Agent: Set up an agent to run at the end of each month to capture the status of all cases.

Record Data: The agent records the case statuses in a separate table specifically created for this purpose.

Reporting: Generate reports based on the data stored in this table to provide an accurate month-end snapshot of case statuses.

References:

Configuring agents in Pega

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

ï‚· Increasing Stage Upweighting: This technique involves gradually increasing the priority or weight of offers in a specific stage of the customer journey, promoting active engagement and progression through the journey stages.

ï‚· Second Stage: In the second stage, which presents available offers, enabling increasing stage upweighting ensures that offers are promoted more actively over time, enhancing visibility and uptake.

ï‚· Reference: Pega's customer journey framework and decision strategies documentation detail how to use stage upweighting to optimize customer engagement and offer promotion (Pega Customer Decision Hub, Customer Journey and Engagement Strategies).

To ensure that all development teams (A, B, and C) are working with the latest version of the shared rulebase, the tasks should be ordered as follows:

Team A publishes the branch to the system of record.

The system of record triggers the job on the automation server.

Automation server requests conflict detection.

The automation server merges the branch to the system of record.

Teams B and C import the application rules within their local environment.

Step by Step Comprehensive Detailed Explanation:

Team A publishes the branch to the system of record:

Explanation: Team A needs to publish their changes to the central repository (system of record) to make them available for integration and further processing.

The system of record triggers the job on the automation server:

Explanation: Once the branch is published, the system of record initiates an automated process to handle the new changes. This step triggers the automation server to start its job.

Automation server requests conflict detection:

Explanation: The automation server needs to check for any conflicts between the newly published branch and the existing codebase. This ensures that any issues are identified and resolved before merging.

The automation server merges the branch to the system of record:

Explanation: After conflict detection and resolution, the automation server merges the changes from the branch into the main codebase in the system of record.

Teams B and C import the application rules within their local environment:

Explanation: Once the merge is complete, Teams B and C can import the updated application rules into their local environments to ensure they are working with the latest version of the rulebase.

References: According to Pega’s best practices for managing distributed development teams, this sequence ensures that changes are properly integrated and conflict-free before being distributed to other teams, promoting consistency and minimizing integration issues.

To address the complaints from customers and prospects about receiving irrelevant offers and products, the following two Pega solutions can be implemented:

Pega Marketing: This solution helps in creating personalized marketing campaigns. By leveraging predictive analytics and customer data, it ensures that the marketing efforts are relevant and targeted. This reduces the chances of customers receiving irrelevant offers.

Customer Decision Hub: This hub centralizes the decision-making process by using real-time data and analytics to personalize interactions with customers. It helps in understanding customer needs and preferences better, thus preventing the delivery of irrelevant offers.

References:

Pega Marketing Overview

Customer Decision Hub