Pega PRPC Development - Fundamentals

Pega's px properties (system properties like pxRequestor, pxResults) are protected and cannot be modified with standard Property-Set. Property-Set-Special is the correct method for modifying these special system properties when necessary. Standard Property-Set only works on user-defined properties.

In Pega's covering feature, both the Cover (parent) and Covered (child) work objects must belong to the same ClassGroup. This requirement ensures proper inheritance and processing rules apply consistently. AccessGroup and WorkPool control different aspects of security and work routing.

Rule-Obj-When rules map to the Fork shape in Pega flows. When a flow execution reaches a Fork, it evaluates Rule-Obj-When conditions to determine which path to follow. Decision shapes use Rule-Declare-Expression or other decision rules, Logic is not a standard flow shape, and Ticket is for wait states.

Rule-Obj-SummaryView is designed to display counts and summaries of work objects grouped by status. It provides aggregate counts like New, Open, Pending, and Resolved. ListView displays detailed lists, GroupBy groups data, and there is no Rule-Obj-Count rule type.

The pxRequestor page contains pxUserIdentifier, which holds the current user's ID. pxFlowInsKey is on pxProcess, pxAssignmentKey is on pxAssignment, and pyID is the work object ID on the primary page. pxRequestor specifically stores information about the user making the request.

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 registers the flow as a valid entry point. Modifying work class HTML or pyFlowType directly is unnecessary and could break system functionality.

When creating a ListView to display operator information, Data-Admin-Operator-ID is the correct Applies To class. This class stores operator data including FullName and UserIdentifier. Rule-Obj-Operator is a rule type, not a data class. Rule-Obj-ListView and Rule-Access-Role-Name are unrelated to operator data storage.

pyWorkCover is the standard Pega property that references the cover work object for a covered work item. It provides a link between a cover and its associated child work objects, allowing navigation and reference in case processing.

Edit Input rules (Rule-Edit-Input) are used to format and convert user input (e.g., stripping dashes from a SSN) before it is saved to a property. Edit Validate rules are used to test property values, not Edit Input.

Pega-ProCom is the standard prerequisite ruleset for all initial application rulesets. It contains essential process commander rules and functionality that applications depend on, making it mandatory for application initialization.

Direct Inheritance is mandatory when creating a class - every class must specify its direct parent class using direct inheritance. Pattern Inheritance is optional and provides additional fallback mechanisms for rule resolution beyond the direct inheritance chain.

Trigger rules in Pega can execute on all database operations including save, update, and deletion. They are designed to respond to any database commit action, making 'All of the above' the correct answer as triggers fire regardless of the specific database operation type.

Pattern inheritance works by removing the trailing dash segment and moving up the hierarchy. For MICO-Finance-, removing the trailing dash gives Mico-Finance as the pattern inheritance parent. This is how Pega's pattern inheritance algorithm navigates the class structure.

pyStatusWork is the Pega property that stores the current status of a work object throughout its lifecycle. It tracks the work item's state (New-Open, Resolved-Completed, etc.) and is essential for workflow management and reporting.

Development (non-standard) rulesets have specific naming constraints: maximum 32 characters, no spaces allowed, cannot use Pega as a prefix (reserved for standard rulesets), and cannot contain special characters. These rules distinguish custom rulesets from Pega's standard rulesets.

According to the Ten Guard Rails of PRPC (PegaRULES Process Commander), application performance should be monitored on a Weekly basis. This regular monitoring cadence ensures performance issues are identified and addressed promptly, maintaining system health.

Prompt Select HTML Property is the correct Pega control for displaying property values in a dropdown (combo box) format. It provides a selectable list of values for user interaction, unlike other options which serve different UI purposes.

PRPC defines multiple standard roles including Process Architect (designs business processes), System Administrator (manages technical infrastructure), and System Architect (builds application rules). All three are valid predefined roles in the Pega platform.

The System Architect role in Pega primarily works with Properties - defining data structures, data types, and property settings. While System Architects may touch other elements, Properties are their core focus. Other roles handle flows, harnesses, and correspondence rules.

Style Sheet templates (CSS files) in Pega are stored in the RULE-FILE-TEXT class. This class handles text-based file storage including CSS, JavaScript, and other text format files, while other classes handle binary or specific file types.