Free Pegasystems PEGACPBA88V1 Practice Exam with Questions & Answers | Set: 2

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)

Property reference: .Address(1).PostalCodeField type: Single record data relationship

Property reference: .ShippingAddress.CityField type: Text

Property reference: .BillingAddress.TelephoneField type: Multiple record data relationship

Property reference: .Address(1).PostalCode

Field type: Single record data relationship

Explanation: The .Address(1).PostalCode property indicates a specific postal code within a single address. The (1) suggests it’s part of an indexed or paged list, but each PostalCode is a single entity within that address record.

Project delivery leader: The Project Delivery Leader is responsible for overseeing the project plan, managing resources, and ensuring that project milestones are met. They play a key role in verifying the project plan and adjusting schedules to manage expectations and ensure timely delivery.

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 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