PEGACPBA88V1 Certified Pega Business Architect 8.8 Questions and Answers

To route cases to specific loan officers based on loan type using business logic, the following steps are typically used in Pega:

Use Decision Rules: Define a decision table or decision tree that maps loan types to specific operators (loan officers).

Configure Routing in the Flow: In the flow rule, configure the assignment shape to use the decision rule to determine the routing based on the loan type.

Route to Operator: Use the "To Operator" routing option, and apply the decision logic to dynamically determine the operator (loan officer).

In this case:

For mortgage loans, the decision rule routes the case to Adam Ross.

For automobile loans, the decision rule routes the case to Julia Samuels.

For equity line loans, the decision rule routes the case to Don Smith.

References:

Pega Academy: Assignments and Routing

Pega Decision Management: Using Business Logic for Routing

The two field types that are specialized versions of the Query field type are:

A. Data reference:

This field type is used to reference data from an external source dynamically. It allows the application to pull in data as needed without storing it directly within the case.

D. Case reference:

This field type is used to reference another case within the Pega application. It is useful for linking related cases and managing dependencies between them.

References:

Pega Academy: Field Types and Usage

Pega Documentation: Query Field and Specialized Field Types

When planning the next Minimum Lovable Product (MLP) release, a Pega Business Architect should focus on the three pillars of case design: Personas and Channels, Case Types, and Data and Interfaces.

Personas and Channels:

Personas: Identify the different user roles (personas) that will interact with the application. Understanding personas helps in designing user experiences that meet their needs.

Channels: Determine the channels (e.g., web, mobile) through which users will interact with the system. This ensures that the application is accessible and user-friendly across different platforms.

Case Types:

Case Types: Define the different types of cases that the application will manage. Case types are fundamental to structuring the application and ensuring that it can handle various processes and workflows efficiently.

Data and Interfaces:

Data: Identify the data required to support the case types and processes. This includes understanding data sources, data structures, and how data will be captured and used.

Interfaces: Determine the interfaces needed to integrate with external systems. Interfaces are crucial for ensuring that the application can interact with other systems and exchange information seamlessly.

References:

Pega Academy: Case Design

Pega Documentation: Minimum Lovable Product (MLP)

 The data fits the business logic: Ensuring data fits the business logic guarantees that it aligns with the defined processes and rules.

To configure a parent case to continue independently of its child cases, you need to adjust the Wait step settings in the parent case. By configuring the Wait step so that users can continue with the parent case process regardless of the child case status, the parent case does not need to wait for the child cases to reach a certain status or be resolved. This allows for parallel processing where the parent case progresses independently of the child cases.

To sort the cases so that the case with the most recent create date appears at the top, you need to select the Highest to Lowest sort type for the Create Date column.

Select Highest to Lowest sort type: This ensures that the most recent date is listed first and the oldest date is listed last.

References:

Pega Academy: Report Definitions

Pega Documentation: Sorting Data in Reports

To route life insurance underwriting assignments to the correct satellite office based on the policy owner's residential address, using business logic is the most appropriate approach. This approach involves:

Define Routing Rules: Create decision rules or decision tables that map the policy owner's residential address to the corresponding satellite office's work queue.

Implement Business Logic: Configure the routing step in the case type to use these decision rules. The business logic will determine the correct work queue based on the address.

Route to Work Queue: The assignment is routed to the work queue of the satellite office that corresponds to the policy owner's residential address.

This method ensures that each assignment is accurately directed to the appropriate office based on predefined business logic.

References:

Pega Academy: Assignments and Routing

Pega Documentation: Using Business Logic for Assignment Routing

Order of Events:

A user clicks the button.

The system applies a data transform.

The order ID value is set to the value of the confirmation number if the system confirms the payment.

The system refreshes the section.

 A user clicks the button.

Explanation: The event sequence starts when the user interacts with the button by clicking it. This is the trigger for the subsequent actions.

MLP sizing leads to more precise resource planning: Accurate sizing of the MLP helps in precise allocation and planning of resources, ensuring that the team can deliver the required functionality within the defined time frame.

Lock the application after 20 minutes of inactivity: You can configure security settings in a mobile channel to automatically lock the application after a specified period of inactivity to enhance security.

The Pega Express phase in which Pega Business Architects plan for future sprints by creating user stories with the Directly Capture Objectives (DCO) discipline is Discover.

Discover Phase:

During the Discover phase, the focus is on understanding the business problem, identifying the scope, and defining the high-level requirements.

Pega Business Architects work with stakeholders to capture objectives directly into the Pega platform, creating user stories and refining the backlog in preparation for future sprints.

References:

Pega Academy: Pega Express Methodology

Pega Documentation: Pega Express Phases and Activities

Pega offers several collaboration tools, each suited for different types of communication and interaction. For an environment where peers exchange ideas about initiatives to retain employees, the best collaboration tool is "Spaces."

Spaces: This tool is designed for collaborative environments where team members can share ideas, discuss initiatives, and collaborate on projects.

Interactive Environment: Spaces provide a platform for ongoing discussions, file sharing, and real-time collaboration, making it ideal for exchanging ideas and initiatives.

References:

Pega Academy: Collaboration Tools

Pega Documentation: Using Spaces for Team Collaboration