PEGAPCSA87V1 Sample Questions & Answers

Pega Platform provides a dedicated feature for formatting case IDs. In the case type's Settings tab, you can define a prefix for work items. This prefix can include text, dates, and other properties, and Pega automatically handles the sequential numbering. This is the standard best practice and does not require custom rule creation in most cases.

When creating a PegaUnit test case, the 'Setup & Cleanup' tab is used to define the test environment. You can specify a data transform to run before the test execution to populate the clipboard with the necessary pages and properties. This ensures the rule is tested under the correct predefined conditions.

Field Level Auditing is the declarative feature designed specifically for this purpose. By opening the property rule for .PermitStatus and enabling auditing on the History tab, the Pega Platform automatically creates History- instances whenever the property value changes, recording the old value, new value, operator, and timestamp. This is the most efficient and best-practice approach.

The 'Attach content' control is specifically designed for handling file attachments. When used in a Pega mobile app, it provides options to upload a file, take a photo with the camera, or record a video, leveraging native device capabilities. The Image control is for displaying images, not capturing them.

This option correctly combines the core Pega features needed. A staged case lifecycle is appropriate for FNOL. A decision shape using a decision tree (or table) is the correct way to automate the complexity evaluation. The routing logic should be configured on the assignment itself to direct it to the correct work queue based on the decision outcome. Finally, an SLA rule with a Goal (e.g., 2 hours) and a Deadline (4 hours) is the standard way to implement the timing requirement on an assignment.

The 'Requestor' scope creates a single instance of the data page for the entire user session. Since the data is static for the session, the 'Do not reload when' refresh strategy is appropriate, meaning the page is loaded once on the first access and then reused throughout the session without making further API calls. 'Thread' scope would create a copy for each case/work item, which is inefficient. 'Node' scope would share the data across all users on the same server node, which is also a valid performance strategy, but 'Requestor' scope precisely matches the 'once per user session' requirement.

A Validate rule is used for business logic validation that involves comparing property values. In this case, it would compare the 'Date of Birth' property with the current date. Edit Validate rules are for single-field format validation (e.g., ensuring a string is a valid email format) and are less suitable for comparisons. Triggers and Declare Expressions are for procedural logic and calculations, not validation.

The pyWorkPage is the standard, system-managed page on the clipboard that holds the data for the currently open case instance. It is the primary page developers inspect when debugging case-related data issues using the Clipboard tool.

A Correspondence rule is needed to define the template of the email, including the subject, body, and placeholders for dynamic data like the Case ID. The 'Send Email' automation shape is then used in the case lifecycle to trigger the sending of this correspondence at the appropriate point in the process.

A Correspondence rule is needed to define the template of the email, including the subject, body, and placeholders for dynamic data like the Case ID. The 'Send Email' automation shape is then used in the case lifecycle to trigger the sending of this correspondence at the appropriate point in the process.

The standard Pega mechanism for localizing text labels is to use Field Value rules. You create a Field Value rule for the base language text (e.g., 'Submit'). Then, you create a copy of that rule into a ruleset specifically for the target language (e.g., a German ruleset) and enter the translated value ('Einreichen'). Pega's localization wizard automates much of this process. This approach is scalable and maintainable.