Pegasystems PEGAPCBA87V1 - Pega Certified Business Architect (PCBA) 87V1

These two use cases can be implemented by using one or more calculated fields because they involve setting the value of a calculated field based on one or more input fields. For example, the cost of painting a banquet hall can be calculated by multiplying the labor rate, the number of hours, and the area of the hall. The cost of an insurance policy can be calculated by adding the base premium and the selected coverage options. Calculated fields can use functions or custom calculations to express the relationship between fields. References: https://academy.pega.com/topic/calculated-values/v1

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

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

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

To send a copy of the Patient visit summary view through email, you need to first create a PDF file of the view by using a Create PDF automation that references the view. Then, you need to add a Send Email step to the case life cycle and enable the option to include attachments. You can then select the PDF file as an attachment and send it to the patient’s email address. The other options are either incorrect or irrelevant for this requirement. References: https://docs-previous.pega.com/automating-work/87/creating-pdf-files https://docs-previous.pega.com/case-management/87/sending-emails

Calculated fields are fields that derive their values from other fields or expressions. You can use calculated fields to implement use cases that require calculations based on user inputs or data sources, such as estimating costs, quoting prices, computing discounts, etc. For example, you can create a calculated field that multiplies the labor hours by the hourly rate to estimate the labor cost for painting a banquet hall, or a calculated field that adds up the premiums for different coverage options to quote the cost of an insurance policy. References: https://community.pega.com/knowledgebase/articles/user-interface/86/creating-calculated-fields

To address this issue, you need to create a bug in Agile Workbench. A bug is a type of work item that represents a defect or an error in an application that prevents it from functioning as expected or meeting the acceptance criteria. You can create bugs during testing or development to track and resolve issues in your application. References: https://community.pega.com/knowledgebase/articles/agile-workbench/86/creating-bugs

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

 This answer is correct because it is the earliest opportunity to configure a user view for a step in a case life cycle in App Studio. A user view is a form that displays fields and controls for users to enter or view data related to a case or an assignment. In App Studio, you can configure a user view for a step after you add that step to the case life cycle by clicking on the View icon next to the step name. References: https://academy.pega.com/library/87/pega-certified-business-architect-pcba-87v1 (Module 9: User Interface)