PEGACPSA88V1 Exam Dumps - Certified Pega System Architect 8.8

To satisfy this security requirement, you can create a new SysAdmin persona with the required access. A persona is a rule that defines the access rights and privileges for a group of users who perform similar tasks in an application. You can create a new persona by copying an existing one and modifying it to suit your needs. In this case, you can copy the Admin persona and add some of the reporting features from the Author persona to create the SysAdmin persona. References: https://community.pega.com/knowledgebase/articles/security/86/personas

 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

Graphical user interface, text, application, email Description automatically generated

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

To configure a solution that requires approvals from the requestor’s manager, division VP, and possibly an accountant based on the total amount, you can use cascading approval using the reporting manager. This model uses a reporting structure to determine who approves a case based on their position in an organizational chart. You can also use a condition to include an accountant in the approval chain if the total amount exceeds a certain threshold. References: https://academy.pega.com/topic/cascading-approval/v1

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

To display the Select flight insurance check box only when the itinerary includes a flight, you can apply a visibility condition (When rule) to the check box. A visibility condition is a rule that determines whether a UI element is visible or hidden based on a logical expression or a reference to another rule. A When rule is a rule that defines a true-false test based on property values, constants, or other factors. References: https://community.pega.com/knowledgebase/articles/user-experience/86/configuring-visibility-conditions

Graphical user interface, text, application Description automatically generated

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

These two statements about Configuration sets are true. Configuration sets are a unified configuration framework that allows for truly upgradeable and dynamic applications. Configuration sets enable the business to control application behavior by providing low-code options for customizing parameters for application features or specific case types. Configuration sets are used to organize Configuration settings with a common element, such as an application feature or specific case type. References: https://academy.pega.com/topic/configuration-sets/v1

You should consider using a field value when the list of allowed values is mostly static or shared across all case types. A field value is a rule that defines a single value for a field that is used in multiple places in an application. Field values are useful when the list of values does not change frequently or when the same values are used in different case types. References: https://community.pega.com/knowledgebase/articles/data-management-and-integration/86/field-values

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 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