Free Pegasystems PEGACPSA23V1 Practice Exam with Questions & Answers | Set: 5

For the requirement where an auditor needs to receive an email notification if the refund is greater than twice the price of the item, it's important to select a participant role that accurately reflects the auditor's involvement in the case.

• B. Interested individual: This role is designed to represent parties who need to be informed about certain events or milestones within a case but are not directly responsible for actioning the case. In this scenario, the auditor's role is to be notified under specific conditions for oversight purposes, making "Interested individual" the appropriate choice. This setup allows the application to send targeted notifications to the auditor without assigning them case responsibilities that are not part of their role.

The other options, such as Customer (Option A), Owner (Option C), and Work queue (Option D), do not accurately represent the auditor's role in relation to the specific notification requirement.

You would typically use a field value in Pega when the list of allowed values is:

B. Mostly static. Field values are best used for lists of allowed values that do not change frequently. They enable the use of predefined, constant values across the application, providing consistent data references for fields that have a set list of options.

Indicating the progress of a case towards resolution is effectively achieved by updating the case status at various steps throughout the case lifecycle. This method provides real-time, visible markers that reflect where the case is in its process, what has been completed, and what steps remain. Updating the case status is a straightforward way to communicate progress to all stakeholders involved, ensuring clarity and transparency in case handling.

In an online retail application, to display a list of ordered products along with images, unit cost, and quantity, and also display the total cost of the order at the bottom of the view, the configuration must include:

• A repeating dynamic layout to list each product, which can be embedded with other dynamic layouts for displaying each product's details including image and cost.
• The total cost should be displayed outside the repeating dynamic layout to ensure that it is presented as a summary of the entire order, rather than repeating with each product entry. This configuration ensures that the user interface is organized and logically separates itemized costs from the total cost.

To identify the cause of an error in an email confirmation from the employee training portal, it's crucial to replicate the scenario and verify that the correct data is being collected and processed. Creating a test case specifically for the employee portal provides a structured approach to test the entire process flow, including form submissions and email outputs. Adding UI assertions ensures that the interface elements are correctly capturing and displaying the data as expected. Running a new Enrollment case allows for end-to-end testing in the real application environment, ensuring that all components interact as intended and the email confirmation is generated correctly.

To ensure that hospital staff can efficiently provide patients with a summary of their visit, the system needs to generate a document (PDF) and then email it. Configuring a "Create PDF" automation that references the detailed Patient visit summary view allows for the automatic generation of a comprehensive document containing all relevant visit details. Following this, adding a "Send Email" step with the capability to include attachments enables the system to attach the newly created PDF to the email sent to the patient. This combination ensures a streamlined process for distributing important healthcare information securely and efficiently.

For a purchase request case type where requests should automatically go to a manager of an employee, the most straightforward configuration is to design a step within the case lifecycle that specifically routes the case to the manager. This routing logic ensures that once an employee submits a purchase request, it is automatically forwarded to their manager for approval, streamlining the workflow and enforcing organizational approval hierarchies.

To ensure that the processing of an Accident Claim case is paused until the resolution of both Vehicle Damage and Body Injury child cases:

A. Add a wait shape to the parent case pausing the parent case until the child cases resolve. The wait shape is used in Pega to halt the process flow until specified conditions are met, in this case, the resolution of both child cases. This ensures that the parent case does not proceed until all necessary assessments and repairs documented in the child cases are completed, providing a coherent and controlled case management process.

In a claims application where customers file home insurance claims and some claims may be investigated for fraud, it is efficient to create two separate case types: one for "Claim" and another for "Fraud Investigation." The Claim case type handles the standard process of filing and processing insurance claims, including the assessment of damages and coordination of payouts. The Fraud Investigation case type is used specifically to handle instances where claims might require additional scrutiny for potential fraudulent activity. This separation allows each case type to be optimized for its specific processes and requirements, enabling parallel processing and specialized handling where necessary.

According to Pega best practices, the "Repair" phase in an automobile insurance claim process is well-suited to be implemented as a child case. This is because the repair phase often involves multiple parties, complex interactions, and could be managed as a separate but linked process to the main claim. Implementing it as a child case allows for focused management of each repair job, clear separation of concerns, and streamlined communication between the adjuster, repair shop, and the customer.