PEGACPSA23V1 Certified Pega System Architect 23 Practice Questions

To ensure that instances of this class can be processed by multiple applications.

To store reusable data objects or define integration assets that are not cases.

To allow for pattern inheritance from the Pega-provided base classes only.

To prevent the class and its associated rules from being included in a ruleset.

Use a 'For Each Page In' action to loop through the source list and an 'Append to' action to add each page to the target list.

Use the 'Set' action with the target set to .ShippingItems and the source set to .LineItems.

Use the 'Append and Map to' action with .ShippingItems as the target and .LineItems as the source.

Use the 'Update Page' action to set the context to .LineItems and then set the values for .ShippingItems.

Create a flow action that displays a section containing a chart control and add it to the portal.

Create a Report Definition that groups by status and counts cases, then reference this report in a chart control within a section displayed in the portal.

Build an activity that queries the database using RDB-List and populates a page list, then use that page list as the source for a chart.

Configure the chart directly in the portal rule, specifying the class and properties to use for the grouping and counting.

A Declare Trigger that fires on save and writes to a history table.

A Security Policy rule configured for property-level tracking.

The History tab of the flow rule where the properties are modified.

A Field-Level Auditing configuration on the class containing the properties.

A privilege rule that checks the income value.

A visibility condition set to 'Condition (expression)' with an associated 'When' rule that evaluates the income property.

A data transform that sets a flag property, which is then used in a 'When' rule.

A Declare OnChange rule that calls an activity to refresh the harness.

An escalation action that triggers a Data Transform to increase urgency.

A goal time of 4 hours with an associated action to increase urgency.

A deadline time of 8 hours with an escalation action to transfer the assignment.

A passed deadline event that triggers a notification to the case owner.

A Declare Expression on the case type to monitor the stage duration.

In the Access Role rule for the 'Clinical Supervisors' role, by adding the report name as a privilege.

In the Report Definition rule, on the 'Report Viewer' tab, by specifying the required access role.

In the Report Definition rule, on the 'Data Access' tab, by adding a filter condition based on the user's access group.

In the shortcut rule for the report, by adding a 'When' rule or privilege to control visibility.

Enabling the 'Enable offline support' option in the mobile channel configuration.

Configuring all Data Pages used in the case types with a 'Reload once per interaction' refresh strategy.

Creating a custom JavaScript function to store data in the device's local storage.

Using only savable Data Pages for all data operations within the offline-enabled case types.

In the flow action rule, add a pre-processing data transform that checks the user's role and the expense amount.

On the Security tab of the flow action rule, specify a privilege that is granted only to the 'Manager' role.

Create a 'When' rule that checks the user's role and use it to control the visibility of the approval button in the section.

In the Access Group for managers, list the specific flow action in the 'Allowed Rules' array.

A Split Join shape in the stage's process flow.

A case-wide optional action.

A multi-step form configured with a screen flow.

A parallel process configured within the case life cycle.