PEGACPSA88V1 Certified Pega System Architect (V8.8) Questions and Answers

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

To enforce these restrictions when requesting an instant loan, you can use a single Validate rule with two conditions one for income and one for credit card debt. A Validate rule is a rule that tests property values for errors or omissions during case processing. You can define multiple conditions in a Validate rule to check whether the property values meet your business requirements. References: https://community.pega.com/knowledgebase/articles/case-management/86/validating-case-data

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

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

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

To achieve the requested behavior, you can use a checkbox and a decision shape to branch the case flow based on whether the customer wants catering or not. You can also use a visibility condition to show or hide the menu preferences and appointment date fields depending on the checkbox value. References: https://community.pega.com/knowledgebase/articles/case-management/88/branching-case-flow-based-decision

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

This statement about configuring application access is true. An access group is a rule that defines the roles and permissions that users have in an application. An access group can list more than one role, but the system uses the most restrictive setting when there is a conflict between roles. For example, if one role allows creating a case and another role denies creating a case, the system denies creating a case for users who belong to both roles. References: https://community.pega.com/knowledgebase/articles/security/86/access-groups

 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

 The context section of a data transform rule defines the scope and applicability of the rule. It specifies the application layer, such as framework or implementation, the class that the rule applies to, and the ruleset version that contains the rule. References: https://community.pega.com/sites/default/files/help_v88/procomhelpmain.htm#rule-/rule-obj-/rule-obj-property/context.htm

This option follows best practices for naming a ruleset in Pega Platform. A ruleset name consists of two parts separated by a colon (:). The first part is an application-specific identifier, such as Credit Check, that is unique within your organization. The second part is a version number that consists of three numeric segments separated by hyphens (-), such as 03-01-02. References: https://community.pega.com/sites/default/files/help_v88/procomhelpmain.htm#rule-/rule-ruleset-/rule-ruleset-name/main.htm

To implement this requirement, you can implement the Repair phase as a child case. A child case is a case that is created and processed as part of another case, called the parent case. A child case can run independently of the parent case and can have its own life cycle, data, and service levels. By using a child case for the Repair phase, you can allow the parent case to continue independently of the child case processes. References: https://community.pega.com/knowledgebase/articles/case-management/88/creating-child-cases

 These two requirements ensure that valid data is used in a case. The data fits the business logic means that the data values are consistent with the rules and conditions that define the case behavior and outcome. The data is the correct field type means that the data values match the expected format and structure of the field properties, such as text, number, date, or email. References: https://community.pega.com/knowledgebase/articles/data-management-and-integration/86/data-types https://community.pega.com/knowledgebase/articles/data-management-and-integration/86/field-values