PEGACPBA88V1 Certified Pega Business Architect 8.8 Questions and Answers

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)

Import stories: When populating the backlog directly from a spreadsheet, the correct approach is to import the stories. Pega allows for importing user stories from spreadsheets to efficiently populate the backlog.

In Pega, optional actions allow users to perform actions that are not part of the primary process flow but can be performed if needed. This is particularly useful for updating user profile information which may not always be required during the order placement stage. By adding a set of optional actions to the case workflow, customers can update any of the user profile pages individually without disrupting the main flow of the case.

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 name of Pega's business architecture design that aligns human intelligence and process automation with business logic to deliver high-value software solutions is Center-out.

Center-out Design:

This approach focuses on designing the core business logic and processes first (the "center") and then extending outwards to include the user interface (UI) and channels.

By centering on the core logic, Pega ensures that the most critical aspects of the business process are well-defined and robust. This approach supports scalability and adaptability as the system grows and evolves.

References:

Pega Academy: Center-out Business Architecture

Pega Documentation: Center-out Design Principles

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

Use Case: "A medical specialist completes their review of an insurance claim, and the system attaches the report to the case."Automation: Create PDF

Use Case: "Employees of a financial services firm receive confirmation when they register for the required certification classes."Automation: Send email

Use Case: "A Fraud department manager receives a mobile notification that an approval request is in their worklist."Automation: Push notification

Use Case: "When an approver rejects an expense report, an employee can modify and resend the report for approval."Automation: Change to a stage

 A medical specialist completes their review of an insurance claim, and the system attaches the report to the case.

Automation: Create PDF

Explanation: In this use case, the system needs to generate a report that can be attached to the case. The appropriate automation for generating documents like reports is creating a PDF. This ensures the report is in a standardized, non-editable format that can be easily attached to the case.

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.

Mobile app color palettes are different for users and CSRs: Configuring distinct mobile app channels is required when you need different UI elements, such as color palettes, for different user groups (e.g., users and CSRs).

Two statements about insights are true:

B. You can search for and select the fields that you want to include in an insight. This allows for customized data visualizations based on selected fields.

C. You can transform data queries into sharable visualizations, making it easy to share insights with others in the organization.

References:

Pega Academy: Insights and Data Visualization

Pega Documentation: Creating and Sharing Insights

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

To achieve the requested behavior in the event center case type:

Create a checkbox for customers to indicate whether they want catering for the event. This allows customers to specify their preference for catering.

Add a decision shape to evaluate whether the customer has checked the catering checkbox. Based on this decision, the case will either proceed to provide a rental rate quote or prompt the customer to choose a menu before receiving a quote.

Configure the menu preferences and appointment date fields with a visibility condition that displays these fields only if the customer selects the catering checkbox. This ensures that customers who do not want catering do not see these fields, streamlining the process.