PEGACPBA88V1 Certified Pega Business Architect 8.8 Questions and Answers

To match the reports to the correct report types:

Average duration and timeliness per assignment:

Report Type: Process Report

Total customer inquiry cases per state per product line:

Report Type: Business Report

Process Reports: Focus on process metrics like the duration and timeliness of assignments.

Business Reports: Focus on business metrics like customer inquiries segmented by state and product line.

References:

Pega Academy: Reporting and Analytics

Pega Documentation: Types of Reports

 Submission: This phase involves the initial contact and filing of the claim, which typically doesn't need to be a separate case as it's an initial action.

Process Step Description: "A user enters information for a car reservation request."Process Step: Collect Information

Process Step Description: "The system evaluates the request type to determine the next step."Process Step: Decision

Process Step Description: "A manager determines whether to approve or reject a timesheet."Process Step: Approval

Process Step Description: "The system notifies the user of the case status by email."Process Step: Automation

A user enters information for a car reservation request.

Process Step: Collect Information

Explanation: This step involves gathering data from the user. In Pega, collecting information typically involves prompting the user to enter necessary details to move the case forward.

To allow a sales manager to approve sales quote proposals by email and from mobile devices, you should add an Approve/Reject step in the case life cycle and enable the approval from email and mobile options. This configuration ensures that the manager can approve or reject the proposals conveniently through email notifications and mobile devices, without needing to access the Pega application directly.

To create a visualization that allows managers to track the number and status of Customer Support Request cases submitted over the last 30 days, follow these steps:

Open the Explore data landing page: This page allows you to create and explore data visualizations.

Create a new insight: Insights help you visualize and analyze data trends and metrics.

References:

Pega Academy: Data Exploration and Visualization

Pega Documentation: Creating Insights

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)

Use a visibility condition on the mobile phone number field to determine whether to show the field: In Pega, visibility conditions are used to control the display of UI elements based on specific conditions. In this case, you would configure the visibility condition on the mobile phone number field to display it only when the checkbox for subscribing to the text messaging service is selected.

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

Add a report widget to the Manager portal dashboard, and then click Publish to default: To ensure that only managers can view the Employee vacation requests report, you need to add the report widget to the Manager portal dashboard and then publish it to the default dashboard. This makes the report accessible only to users who have access to the Manager portal.

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

Field: Total hours for each type of time tracked (work, vacation, sick)Method: Calculation

Field: Cumulative total of all hours for the weekMethod: Calculation

Field: Updated vacation and sick time balancesMethod: Data transform

Total hours for each type of time tracked (work, vacation, sick)

Method: Calculation

Explanation: The total hours for each type of time (work, vacation, sick) are derived by summing up the respective hours entered by the employee for each day. This involves simple arithmetic operations which are best handled by a calculation rule in Pega.

 A sales representative wants to quote the cost of an insurance policy based on selected coverage options: Calculated fields can dynamically determine the cost based on selected options.