PEGAPCBA87V1 Pega Certified Business Architect (PCBA) 87V1 Questions and Answers

This requirement can be satisfied by using a Wait step with a Timer wait type that pauses a case until a set date/time interval expires or until a reference date/time is reached. In this case, the Wait step can be configured to pause the Accident Claim case for 48 hours after the accident date/time property value. The other requirements do not involve pausing a case based on a timer or a case dependency, but rather on user actions or inputs. References: https://academy.pega.com/topic/case-workflow-dependency/v1

To inform a user by email when an assignment is added to the user’s worklist, you need to configure the case type to send assignment notifications to assigned users. This option enables email notifications for all assignments in the case type. The other options are either incorrect or irrelevant for this requirement. References: https://docs-previous.pega.com/case-management/87/sending-email-notifications

These two case types can support the scenario of filing home insurance claims with items of loss and potential fraud investigation. Items of loss can be implemented as a child case type that represents each item that is claimed by the customer. Fraud investigation can be implemented as a parallel process that runs in the background while the main claim process is ongoing. The other options are either incorrect or irrelevant for this scenario. References: https://academy.pega.com/topic/child-cases/v1 https://academy.pega.com/topic/parallel-processes/v1

To configure the case type to verify that the value of Date account opened is in the past, you need to use a validation condition. A validation condition is a rule that checks whether the value of a field meets a specified criterion. You can use a validation condition for the Date account opened field that compares it with the current date and displays an error message if it is not in the past. References: https://community.pega.com/knowledgebase/articles/user-interface/86/configuring-validation-conditions

To ensure that valid data is used in a case, you need to make sure that the data fits the business logic and the data is the correct field type. The data fits the business logic means that the data conforms to the rules and constraints that define the business problem and solution. For example, you can use validations, calculations, and dependencies to ensure that the data fits the business logic. The data is the correct field type means that the data matches the expected format and structure of the field that stores or displays it. For example, you can use different types of fields and controls to ensure that the data is the correct field type. References: https://community.pega.com/knowledgebase/articles/user-interface/86/ensuring-valid-data-used-case

Before you add fields to a view, you need to decide how users enter values into the field and whether the fields require a data source. These decisions determine the type and configuration of the fields that you add to the view. For example, you can use different types of controls to allow users to enter values in different ways, such as text inputs, drop-down lists, radio buttons, etc. You can also use different types of data sources to populate the fields with values from your application data or external systems, such as data pages, report definitions, connectors, etc. References: https://community.pega.com/knowledgebase/articles/user-interface/86/adding-fields-view