PEGACPSA88V1 Questions and Answers

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

These two field types are specialized versions of the Query field type. A Query field type allows users to select a value from a list that is populated by running a report definition rule or by referencing another field value rule. A Case reference field type allows users to select an existing case from a list that is populated by running a report definition rule on the Work- class or one of its subclasses. A Data reference field type allows users to select an existing data object from a list that is populated by running a report definition rule on a specific data class. References: https://community.pega.com/knowledgebase/articles/user-experience/86/configuring-field-types

To fulfill this requirement, you can create two new work queues one for editors and one for actors. Work queues are used to route tasks to groups of users who share similar skills or responsibilities. You can then route Edit Script tasks to the editors work queue and Record Script tasks to the actors work queue. References: https://community.pega.com/knowledgebase/articles/case-management/88/routing-work-queues

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

 This option requires you to configure distinct mobile app channels because it involves customizing the look and feel of the mobile app for different user groups. A mobile app channel is a configuration layer that defines how users interact with your application on mobile devices. You can create multiple mobile app channels for different user groups or personas and apply different branding, security, or functionality settings to each channel. References: https://community.pega.com/knowledgebase/articles/mobile/86/configuring-mobile-app-channels

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

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 basic condition for the Search duplicate cases step is to compare the issue type of the current case with the issue type of existing cases. This way, only cases that have the same issue type are considered as potential duplicates. References: https://community.pega.com/knowledgebase/articles/case-management/88/searching-duplicate-cases

Graphical user interface, text, application Description automatically generated

Optional actions are actions that users can perform at any time during a stage in the case workflow. They are not required to advance the case to the next stage or step. Optional actions can be used to allow customers to update any of the user profile pages individually during the order placement stage. References: https://community.pega.com/knowledgebase/articles/case-management/88/configuring-optional-actions