PEGACPSA88V1 Certified Pega System Architect 8.8 Question and Answers

To meet this requirement, you can design a case with a step that routes to the manager. A step is an action that users or systems perform to advance a case toward resolution. You can configure a step to route to a specific user or group of users based on their role, skill, availability, or reporting structure. References: https://community.pega.com/knowledgebase/articles/case-management/88/adding-steps-case-life-cycle

To meet the requirement, you can add an Identify service animal process within the Travel booking case life cycle and apply a condition to determine when to run the process. The condition can be based on a property that indicates whether the passenger is traveling with a service animal or not. References: https://community.pega.com/knowledgebase/articles/case-management/88/adding-processes-case-life-cycle

The Constellation design system is a set of UI/UX templates, patterns, and components that enable faster and easier development of Pega applications. It improves context switching or multitasking by allowing users to work on multiple tasks in parallel using dynamic containers and tabs. It also uses a modular design that enables reuse and customization of UI elements across applications. References: https://community.pega.com/knowledgebase/articles/user-experience/88/introducing-pega-constellation-design-system

 To create a visualization that allows managers in the Customer Service division to track the number and status of Customer Support Request cases submitted over the last 30 days, you can open the Explore data landing page, and then create a new insight. An insight is a visualization of data that you can use to monitor key performance indicators, identify trends, and discover opportunities for improvement. You can create insights from the Explore data landing page in App Studio. References: https://community.pega.com/knowledgebase/articles/reporting/86/creating-insights

These two statements about data records are true. Data records are values for the fields that are associated with a specific data object, such as a customer or a product. Data records need unique user-generated IDs to identify each record in the data object. Data records define permissible values for data fields, which limit the input values to valid options, reduce errors, and allow for automation. References: https://academy.pega.com/topic/data-records/v4

To configure the account information page, you can select Copy from a data page on the page property. This option copies the data from the data page to the clipboard page when the case is created and does not update it when the case is further processed. A data page is a rule that defines how and when to load data into memory for use by an application. References: https://community.pega.com/knowledgebase/articles/data-management-and-integration/86/data-pages

When adding an external data source to a data object, a data transform is automatically generated to map the application data model to the connector. A data transform is a rule that defines how to convert data that is in one format and class (the source) into data of another format and class (the target). A connector is a rule that defines how your application exchanges information with an external system. References: https://academy.pega.com/topic/data-records/v4 https://community.pega.com/knowledgebase/articles/data-management-and-integration/86/connectors

To implement this requirement, you can configure a data page to store the make, model, and year vehicle data and configure a connection to an external system of record that contains the make, model, and year vehicle data. A data page is a rule that defines how and when to load data into memory for use by an application. You can configure a data page to source its data from an external system by using connectors or integrations. This way, you can access up-to-date vehicle data from an external database or web service without storing it locally in your application. References: https://community.pega.com/knowledgebase/articles/data-management-and-integration/86/data-pages https://community.pega.com/knowledgebase/articles/data-management-and-integration/86/sourcing-data-page-data-external-systems

To determine the recommended meal plan based on the number of people in the household and dietary restrictions, you can use a decision table and a decision shape. A decision table is a rule that derives values that have one of a few possible outcomes, where each outcome can result from a test of a condition that includes multiple variables. A decision shape is a shape that you can add to a flow to branch the flow based on the result of a decision rule, such as a decision table. References: https://academy.pega.com/topic/decision-tables/v1

To ensure the email includes the case ID for the survey, you can use the Insert Property feature of a Send Email step to add the case ID when composing the custom message. This way, you can dynamically insert the value of any property in your email message. References: https://community.pega.com/knowledgebase/articles/case-management/88/sending-emails

The project delivery leader is responsible for managing the project plan, scope, budget, and timeline, as well as communicating with stakeholders and resolving issues. The project delivery leader should be contacted to verify the project plan and manage expectations for the release schedule when the scope of the project exceeds the original estimates. References: https://academy.pega.com/library/82/pega-project-delivery-methodology

This statement about channel interfaces is true. A channel interface is a user interface that allows users to interact with an application through various channels, such as web, mobile, email, chatbot, or voice. A channel interface allows you to adjust your application to your specific business needs by creating tailored and interactive user interfaces. Channels are created from templates that include predefined layouts and navigation for use in your application. References: https://academy.pega.com/topic/channel-interfaces/v1

To localize correspondence into a language that is unavailable in the Pega language pack, you can create the Translation rule manually and include the rule in the application ruleset. A Translation rule is a rule that defines how to translate text from one language to another. You can create a Translation rule manually by using the Create menu in Dev Studio and selecting Rule > Integration-Resources > Translation. You can then specify the source and target languages, the text to be translated, and the translated text. You can also use a decision table or a connector to provide the translated text. You must include the Translation rule in the application ruleset so that it can be used by the application. References: https://community.pega.com/knowledgebase/articles/integration/86/translation-rules

To meet this requirement, you need to set the deadline in the service level to 3 days. The deadline defines when to take action because a step or case is past due. The deadline interval is measured from when an assignment is ready for a user. References: https://academy.pega.com/topic/deadline-interval/v1