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.

For a reservation process that includes various components like flights, hotel rooms, and rental cars, showing an option for travel insurance specifically when a flight is part of the itinerary necessitates dynamic UI adjustments based on the user ' s selections.

A. A visible when condition applied to the check box : This configuration directly supports the requirement by dynamically controlling the visibility of the travel insurance check box based on whether the itinerary includes a flight. A Visible When condition can evaluate the presence of a flight in the itinerary and accordingly display or hide the insurance option, providing a tailored user experience.

Action sets (B) typically define user interactions with UI elements but are not used for conditionally displaying those elements based on other case data. Declare expressions with forward chaining (C) are used for calculating values rather than controlling UI element visibility. Validate rules (D) ensure data integrity during submission and are not involved in UI visibility conditions.

To implement a requirement where different processes are applied based on customer card types:

C. Add a custom condition to start the process by testing the card type. This solution involves setting a condition at the beginning of the Employment Information process that checks the type of credit card (standard or platinum). If the condition identifies a platinum card, the process is skipped, aligning the process flow with the specific requirements of different cardholders.

Create PDF: In the context of a medical specialist completing their review of an insurance claim, the automation likely involves generating a formal document, such as a report, which can then be attached to the case. In Pega, this is typically accomplished through a PDF generation functionality, which converts the review findings into a document that can be attached to the case.

Send email: Employees receiving confirmation upon registration is typically handled via automated email notifications. When an employee registers for certification classes, an automated email would serve as a confirmation for the registration. This is a common practice in business process management systems to confirm and communicate actions.

Push notification: A Fraud department manager receiving a notification about an approval request in their worklist is a scenario suited for push notifications. These are immediate alerts that can be sent to a user ' s mobile device or computer, prompting them to take action or informing them of an important event.

Change to a stage: If an approver rejects an expense report, allowing the employee to modify and resend it for approval would involve workflow automation. This typically means that the case needs to be moved back to a previous stage in the process where the employee can make the necessary changes before resubmitting it for approval.

References:

These use cases are aligned with the automation capabilities of Pega ' s BPM (Business Process Management) tools, which are designed to handle such scenarios.

The Pega Platform documentation and help resources provide guidance on configuring these types of automations within the case management framework.

This question appears to be a duplicate of Question No: 73 and therefore the answer and explanation remain consistent. " Schedule Interview " and " Notify Candidate " are steps that precisely describe the corresponding actions in the job application process. Naming steps in this manner ensures that the purpose and outcome of each step are immediately clear to anyone involved in the process or reviewing the case.

When configuring a data page that needs to retrieve details of a single record, the appropriate source to use is:

D. Lookup. Lookup is specifically used in Pega to retrieve a single record based on a key or a set of keys from a data type. This makes it suitable for data pages that are intended to provide detailed information about a particular entity, ensuring efficient and accurate data retrieval based on specific criteria.

Given the updated business requirement allowing the parent Accident Claim case to continue independently of the status of the child cases:

D. Configure the step so that users can continue with the parent case process regardless of child case status. The Wait step previously used to pause the parent case should be removed or configured to not halt the parent case processing, thereby permitting the parent case to proceed without dependency on the child cases ' progress or resolution. This change reflects the new requirement for the parent case to operate independently from the Vehicle Damage (VD-001) and Body Injury (BI-001) child cases.

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 a form supports accessibility, especially when enabling a user to specify a date, using an interface that is intuitive and easy to navigate is key. Among the provided options, a calendar control that displays an entire month is the most accessible and user-friendly method for date selection.

C. Use a calendar control that displays an entire month : This method provides a visual and interactive way for users to select a date, offering both keyboard navigation and screen reader support, making it accessible to users with a wide range of disabilities, including visual impairments. A month view gives users an overview of the dates, allowing for easy selection without requiring manual date entry, which can be prone to errors and less accessible for some users.

Configuring a text box for date entry (A) may not be as accessible because it relies on users correctly typing the date, which can be challenging for some people. Using a calendar control that displays an entire year (B) can be overwhelming and less practical for date selection. Providing separate controls for month, day, and year (D) could increase complexity and potentially decrease accessibility due to the need to navigate between multiple controls.

Insights in Pega are designed to help users analyze and visualize data:

A. You can search for and select the fields that you want to include in an insight. This feature allows users to customize insights by choosing which data fields to analyze, enabling focused and relevant analyses.

B. You can transform data queries into shareable visualizations. Insights provide the capability to turn complex data queries into visual representations, such as charts or graphs, which can be easily understood and shared, enhancing the decision-making process.