Pega PRMC Platform Fundamentals

Property-Map-Value passes a single row input to a Rule-Obj-MapValue. Property-Map-ValuePair passes a single row input AND a single column input to the Rule-Obj-MapValue, allowing lookup based on two dimensions. This is the key difference between the two methods.

When an access role is specified at a parent class in Pega, it applies to that parent class AND all its child classes by default. However, if a child class has an explicit access rule that overrides the inherited role, the override takes precedence for that child class. This is inheritance with override capability.

Trigger rules execute whenever database operations occur on objects in PEGA. This includes creating new objects (save), modifying existing objects (update), and removing objects (delete) from the database. The trigger mechanism allows automatic execution of business logic at these data modification points.

Declare rules execute at multiple points in PEGA processing. Some run during flow execution as control moves between tasks, others at activity step boundaries after method invocation but before transitions, and Declare Trigger rules specifically run when objects are committed to the database. The declare keyword provides automatic rule execution across these contexts.

In PEGA SLA definitions, Goal and Deadline are single-point thresholds that can each be specified only once. However, the Late condition can be defined multiple times to create escalating urgency levels (for example, 25% past deadline, 50% past deadline, etc.). This allows progressive notification and handling as violations become more severe.

In Pega, pattern inheritance searches for parent classes by truncating segments separated by dashes. For the class MICO-Finance-, removing the trailing dash and the last segment yields MICO-Finance (or case-normalized Mico-Finance) as its pattern parent.

PEGA organizational hierarchy follows a top-down structure starting with Organization (the highest level encompassing the entire enterprise), then Division (major business units within the organization), and finally Unit (the smallest organizational subdivision). This structure supports work assignment, reporting, and access control throughout the system.

SmartBuild in PEGA follows a logical development sequence starting with Class Structure (defining data model), then Properties (individual attributes), User Interface (forms and screens for user interaction), and finally Activities (business logic and processing). This sequence ensures foundational elements are established before building dependent components.

The Show-Page method is the standard PEGA function for displaying pages including XML-formatted content. It renders the specified HTML or XML stream to the user interface. The other options (Show-XML, Apply-Parse-XML, Display-XML) are not valid standard PEGA methods for this purpose.

Operators share a workbasket when their operator IDs belong to the same WorkGroup in PEGA. WorkGroups determine which workbaskets are visible to which operators, allowing multiple operators to access and process assignments from the same shared queue. ClassGroup, WorkPool, and AccessGroup serve different purposes and don't control workbasket sharing.

All the listed formats are valid Work ID patterns in PEGA. W- (simple prefix), W-TCS (prefix with organizational identifier), and TCS-W- (reverse format) are all acceptable patterns. The Work ID format is flexible and can be configured with different prefix and suffix combinations to match organizational naming conventions.

Prompt Select HTML Property is the correct PEGA property for displaying values in a dropdown (combo box) format. It renders a selectable list of options for user input. The other options are not valid property types in PEGA for this purpose - this is the standard built-in property for dropdown selection.

In Pega, HTML properties (now known as Control rules) are used to format and customize how property values are displayed or entered on a user interface, allowing developers to customize presentation and behavior.

Standard px properties in PEGA are protected system properties that normally cannot be modified directly. Property-Set and Property-Set-X are for regular properties. Property-Set-Special is the specific method designed to modify protected px properties when necessary. This special method is required because px properties are read-only by design to prevent accidental system corruption.

The Integrator shape in PEGA is specifically designed for sending data to and receiving data from external systems. It handles the communication interface, data transformation, and integration logic required for external system interactions. Ticket, Fork, and Split-Join shapes serve different flow processing purposes and are not for external system communication.

Cover and Covered objects in PEGA must belong to the same ClassGroup to maintain proper object relationships. The Cover-Covered relationship links related work objects within the same class group hierarchy, allowing parent-child associations. AccessGroup and WorkPool control different aspects (security and work assignment) and don't determine cover relationships.

Rule-Obj-When represents conditional branching in PEGA flows and is visually represented by a fork (diamond) shape in flow diagrams. This shape indicates that the flow will take different paths based on conditional logic evaluation. Decision and Logic shapes represent different flow elements in PEGA.

Page Context defines a specific page scope within the clipboard structure where rule actions will be executed. It allows rules to target properties on a particular page rather than operating broadly. The $Any and $None keywords are related but serve different purposes in PEGA expression syntax.

By default, assignments in PEGA have the harness property set to 'Perform', which determines which harness is used to display the assignment. This setting controls the user interface presented to users when they work on the assignment. New, Confirm, and Review are other valid harness modes but not the default.