PEGACPBA88V1 Certified Pega Business Architect 8.8 Question and Answers

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

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.

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

For an application to process a new customer loyalty account with data stored in a data relationship with an external data source, you should create a data reference field.

Data Reference Field: This field type allows the application to reference and use data from an external source without embedding it directly within the case. This is suitable for maintaining up-to-date information and integrating with external systems.

References:

Pega Academy: Data Management

Pega Documentation: Data Relationships and Integration

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.

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)

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.

In Pega, the status of a case can be updated based on actions taken within the process. The status change to "Pending-Investigation" is tied to the completion of the "Review claim" step:

Review Claim Step Configuration: The "Review claim" step is configured to set the case status to "Pending-Investigation" upon its completion.

Status Change Trigger: The status update happens automatically when the "Review claim" step completes, indicating that the case is now waiting for the investigation to be performed.

This ensures that stakeholders are aware of the case's progress and that the system correctly reflects the current state of the case.

References:

Pega Academy: Configuring Case Status

Pega Documentation: Steps and Processes

To meet the requirement that transaction disputes must be resolved within 3 days, you need to set the deadline in the service level agreement (SLA) to 3 days. The deadline specifies the maximum time allowed to resolve the transaction disputes, ensuring that the case is handled within the required timeframe.

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.

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.