PEGACPSA24V1 Sample Questions & Answers

A Summary report is designed for aggregation. By grouping the report data by the package status property (pyStatusWork) and using the Count aggregate function, the report will display exactly what is required: a count of packages for each distinct status ('Pending', 'In Transit', etc.). A List report would simply show all individual packages.

PegaUnit tests use assertions to automatically validate outcomes. The correct approach is to define the input data (e.g., set .PurchaseAmount to 1500) on the Setup & Cleanup tab, and then on the Results tab, create an assertion of type 'Property' to validate that the output property .CustomerLevel has the expected value of "Gold" after the data transform runs.

The Wait step is specifically designed for this purpose. It allows a case to pause its processing at a specific point in the flow until one or more defined conditions are met, such as a property being set to a specific value or a certain amount of time elapsing. In this scenario, it would be configured to wait until the property holding the vendor's clearance code is no longer null.

The PegaRULES:User4 role provides basic user-level access, which includes the ability to view and run reports that they have access to. The PegaRULES:WorkMgr4 role has additional privileges, including the ability to create and modify reports. The PegaRULES:SysAdm4 and PegaRULES:SysArch4 roles have even higher levels of administrative and development privileges.

Swipe actions are configured directly on the repeating layout (table) that displays the worklist. In the layout's properties, you can define actions for left and right swipes, mapping them to specific flow actions (like 'Approve' or 'Reject'). This provides a native mobile experience for users.

The Set action in a data transform is used for assigning values. When the source and target are both page properties of the same class, the Set action performs a full page copy, copying all the properties from the source page (TempAddress) to the target page (PermanentAddress). This is the standard and most direct way to copy one page to another.

This requirement calls for an exact match on multiple criteria plus a time-based condition. Basic conditions are perfect for this, as they require all specified properties (Customer ID, Product SKU) to match. The time constraint is handled by adding a filter condition on the pxCreateDateTime property, not by using weighted conditions, which are better for 'fuzzy' matching where not all properties must be identical.

In the Tracer's output, the execution of a rule is typically shown as a nested block starting with a 'Begin' event and ending with an 'End' event. The 'Begin' event for the data transform will show which parent rule (e.g., an activity step, a flow action, another data transform) called it. By locating the Data Transform End event and scrolling up to its corresponding Data Transform Begin event, the developer can see the parent context in the event hierarchy.

Pega's localization framework relies heavily on Field Value rules. A developer defines the base text (e.g., 'First Name') in a Field Value rule and then creates translated versions of that same rule for different locales (e.g., 'es_MX' for Mexican Spanish, 'fr_CA' for Canadian French). At runtime, Pega automatically selects the appropriate Field Value based on the user's locale settings, displaying the correct language.