PEGACPSA23V1 Sample Questions & Answers

The Constellation architecture uses a view-based, design system-driven approach and does not use traditional section rules for UI composition. Views in Constellation are built from a library of prescribed components in App Studio. Traditional section rules are part of the classic, non-Constellation UI architecture.

The 'Reload if older than' refresh strategy is designed specifically for this use case. It allows the system to serve a cached version of the data page unless the specified time interval (in seconds) has elapsed since it was last loaded, at which point it will be reloaded from the source.

An Edit Validate rule is used for client-side, format-based validation of a single property using Java. By creating an Edit Validate rule with the required logic (e.g., a regular expression) and referencing it on the Advanced tab of the Property rule form, you ensure that this format validation is applied consistently wherever the property is used.

The Create Case smart shape is designed specifically to instantiate new cases, including child cases. It can be placed after a decision shape that checks the order value, ensuring the 'Insured Shipping' child case is created only when the condition (order value > $1000) is met.

The pySetFieldDefaults data transform is automatically invoked when a case is created. It is the standard, best-practice location for setting default values for case properties. Modifying this rule is the most efficient and guardrail-compliant way to meet the requirement.

Pega Platform provides built-in support for mobile swipe gestures. Within the properties of a repeating layout used in a mobile channel, you can directly configure 'Swipe actions'. This allows you to define actions and associate them with icons that are revealed when the user swipes left or right on a list item.

The 'Group By' function is fundamental to creating summary reports. Applying it to the stage column will aggregate all records by their stage name.

To get the total number of cases for each group, you need to use a summary function. Applying 'Count' to a unique identifier like the case ID will provide the correct total for each grouped stage.

Security policies are rules that define password requirements such as length, complexity, expiration, and history. The requirement to check against the last three passwords would be configured in the 'Password history' section of a Security Policy rule, which is then associated with an Authentication Service.

This is the standard pattern for cascading controls. The 'On Change - Refresh Section' action on the parent control ('Country') posts the selected value to the clipboard. The data page for the child control ('State/Province') should be configured to accept the country value as a parameter, so when the section refreshes, the data page reloads with the correct, filtered list of states.

Alternate stages are designed for processes that are not part of the normal course of events but can be invoked when needed. Creating an 'SFU Review' alternate stage and providing a case-wide action (or a stage-specific action for Investigation/Adjudication) allows users to divert the case for the special review and then potentially return to the primary path.