Pega PRCP Fundamentals

A ticket event interrupts processing and transfers control. It impacts all active, executing flows related to the work object that contain the designated ticket, rather than affecting only one flow or all flows unconditionally.

ServiceLevel rules used to set SLAs are found under the Process menu in PRPC. SLAs are fundamentally about process timing and service levels, which is why they're categorized under Process rather than Technical, SysAdmin, or Security menus.

Activity Steps is not an available option under Event Types To Trace in the Tracer. The Tracer can trace Flow, Declare Constraint, Declare Decision Tree, and other rule types, but individual Activity Steps are not a selectable trace event category.

The Property-Map-Value method evaluates a 1D map value rule using a single row input. The Property-Map-ValuePair method evaluates a 2D map value rule, which accepts both a row input and a column input to look up a value.

Services are the mechanism for external systems to access PRPC data and processes. Services expose PRPC functionality externally. Connectors are used by PRPC to call external systems, not the reverse. Servers is too generic and All the above is incorrect because only Services enable inbound access.

Correspondence Types are rule instances of type Rule-CorrType. This is the specific rule type for defining correspondence templates in PRPC. Rule-Obj-Corr and Rule-Corr are not the correct rule types for correspondence type definitions.

In SLAs, only the Late condition can be specified as repeated. Goal and Deadline are one-time events that fire at specific intervals. Late conditions can recur to indicate continued violation beyond the deadline, making it the only repeatable SLA component.

In Pega SmartBuild, the development follows a logical sequence: first establish the Class Structure as the foundation, then define Properties to hold data, create the User Interface for user interaction, and finally implement Activities for business logic processing. This sequence ensures dependencies are met - properties need a class structure, UI needs properties to display, and activities operate on both.

The Show-Page method is the standard Pega method for displaying XML-formatted output. It serializes page data into XML format for display or transmission. Options B, C, and D are not valid Pega methods for this purpose.

In Pega, operators can share a workbasket when their operator IDs belong to the same WorkGroup. WorkGroups define which operators can access and process assignments from shared workbaskets. ClassGroups, WorkPools, and AccessGroups serve different purposes in Pega security and organization.

px properties are protected system properties in Pega that require special methods to modify. Property-Set-Special is the designated method for updating px properties, while standard Property-Set and Property-Set-X cannot modify them. They can be changed, but only through this specialized method.

In Pega's covering mechanism, both the cover work object and covered work objects must belong to the same ClassGroup. This ensures structural consistency and proper inheritance relationships. AccessGroups control security, WorkPools manage assignment routing, but ClassGroup membership is the requirement for covering.

Rule-Obj-When rules in Pega are mapped to the Fork shape in flow diagrams. The Fork shape represents conditional branching based on when conditions, not decision logic (which uses Decision shape), sequential logic, or ticket processing.

A SummaryView rule (Rule-Obj-SummaryView) is designed to display aggregated data, such as counts, averages, or sums grouped by specific fields (like work object status). ListView rules display detailed row listings, and the other rule types do not exist.

The pxRequestor page contains pxUserIdentifier, which holds the operator's user identifier. pxFlowInsKey and pxAssignmentKey are found on other pages (pyWorkPage or assignment pages), and pyID is a work object property, not a requestor page property.

To add a work type to the New selection list, create a new flow and check the 'Creates a New Work Object' setting. This automatically adds the flow's work type to the list. Creating just a work class won't add it to the list, and manually updating HTML is not the correct approach.

When creating a ListView for operator information (Full Names and User Identifiers), the 'Applies To' class should be Data-Admin-Operator-ID. This class contains operator data. Rule-Obj-Operator is for operator rule instances, Rule-Obj-ListView is for ListView definitions themselves, and Rule-Access-Role-Name is for access control.

pyWorkCover is the conventional Pega page name that contains a covering work object. This page holds the cover object reference. pyWorkPage is the main work page, pyObjectCover and pyObjectWork are not standard Pega page names.

Edit Input rules (Rule-Edit-Input) are used to convert input data into a standard format. They normalize user input before processing. They are not used for testing property values, database operations, or enforcing comparison relationships.

Pega-ProCom is the prerequisite ruleset for all initial application rulesets in Pega. It contains foundational process commander functionality. PegaApp and Pega-Rules are not the correct prerequisites, and a prerequisite is necessary.