PEGACPBA88V1 Questions and Answers

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

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.

As a project nears the end of the Prepare phase, the project plan should include:

B. Epics and user stories:

These are essential for defining the work to be done in future sprints. They provide detailed descriptions of the functionality and requirements that need to be developed and tested.

C. RAID log (Risks, Actions, Issues, and Decisions):

This log is critical for tracking potential risks, ongoing actions, issues that need resolution, and decisions made during the project. It helps in managing and mitigating risks and ensures that the project stays on track.

References:

Pega Academy: Project Planning and Management

Pega Documentation: Prepare Phase Activities and Deliverables

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

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.

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

The basic condition for identifying duplicate cases, such as IT tickets for the same issue, is to check if the issue type is the same. By configuring the Search duplicate cases step to identify cases where the issue type is the same, you can effectively identify and manage duplicate IT tickets related to common problems like "the office Wi-Fi is down."

 Identify key risks with the technical architecture: Before moving to the next phase, it is important to identify and assess any risks associated with the technical architecture. This allows the team to develop mitigation strategies and ensure that the architecture supports the business requirements and can scale appropriately.

When a service level (SLA) adjusts the assignment urgency to 100 upon the goal interval lapsing, the following impacts occur:

Urgency Value Adjustment: The urgency value of the assignment is set to 100, indicating high priority.

Continued SLA Processing: Other SLA processing, such as escalating actions and notifications, continues as configured.

Urgency Cap: The urgency value remains at 100, which is the maximum urgency, but this does not halt other service level processing.

Therefore, setting the urgency to 100 indicates maximum priority but allows for continued SLA actions such as further escalation and notifications.

References:

Pega Academy: Service Level Agreements

Pega Documentation: SLA Urgency and Escalation Mechanisms

User interfaces are also known as channel interfaces: In Pega, user interfaces are referred to as channel interfaces because they represent the different ways users interact with the application, such as through web, mobile, or other channels.