Pega PRPC Fundamentals

In PEGA, operators who belong to the same WorkGroup can share the same workbasket. Workgroups determine which workbaskets an operator can access. Classgroups are for rule organization, WorkPools are related to work classes, and AccessGroups control security permissions - not workbasket sharing.

In Pega, 'HTML' type properties or rules containing HTML code are primarily used for rendering and customizing the display of user interfaces, screens, and fields, rather than manipulating XML or simply displaying escape characters.

Pega properties prefixed with 'px' are system-managed and read-only. They cannot be modified using standard methods like Property-Set. The special method Property-Set-Special is designed specifically to modify these system-controlled px properties.

PEGA HTML provides several directives for working with properties: Reference (for reading property values), Lookup ( for searching), With (for context), and Save (for persisting). All of these are valid HTML directives in PEGA for property manipulation.

PEGA rule resolution follows specific rules: when version 10-27 is in the rule set list, it can access 10-27 (major.minor), all patches of 10-27 (10-27-1 through 10-27-99), and the highest patch of the previous minor version (10-26-1). It cannot access versions like 10-99-99 which are in a different minor version branch.

In PEGA, the Review harness is a read-only harness that displays work object information without allowing modifications. Perform and Re-Open harnesses allow user input and changes, New harness is for creating new work, and Perform_Buttons is a subsection for buttons - none of these are read-only.

The PEGA tracer cannot trace flows that are called from within an activity step. The tracer can trace activities and other rule types directly, but when a flow is invoked from an activity (using something like the Flow-Execute method), the tracer cannot follow the flow execution. You would need to trace the flow separately or use breakpoints.

Activities in Pega can be referenced and called from other activities, from flow shapes in flows, and from flow actions that users interact with during case processing. Models and constraints are different rule types that don't directly reference activities.

Pega's implementation methodology, known as Direct Capture of Objectives (DCO), is based on IBM's Rational Unified Process (RUP). This iterative approach emphasizes visual specification, use-case driven development, and direct execution of requirements without traditional coding.

All routing activities in Pega return their result in a standard parameter named AssignTo. This parameter contains the operator or work queue to which the assignment was routed, enabling the system to direct work appropriately.

In Pega's reference structure, Applications reference Access Groups (which define which application an operator sees), and Access Groups reference Operator IDs (which define operators belonging to that group). This creates a proper hierarchical reference chain from Application to Access Group to Operator ID.

Page-New is the correct method for creating top-level pages on the clipboard in Pega. Obj-Open is used to retrieve existing pages from the database into the clipboard, not create new ones. The other options are not valid Pega methods.

Service Level Agreements in Pega can be configured at both the Work Object level (for tracking time on the entire case) and at the Assignment level (for tracking time on individual user tasks). This allows for different urgency and escalation rules at different granularities.

The Rule Inspector tool identifies and displays rules that are actively being used during case processing and UI rendering. It specifically detects Properties, Harnesses, and Sections which are the UI and data structure rules that are currently active. When conditions are logic rules that evaluate but aren't typically surfaced in the inspector.

In a Rule-Declare-Expression, the Page Context identifies the embedded page (or page list/group property context) on which the properties referenced in the expression are defined, ensuring Pega resolves the properties relative to that correct context.

Pega PRPC ships with three default user accounts for initial setup and system management: Administrator for system administration, System Architect for technical configuration and rule development, and Work Manager for work queue and assignment management. 'Operator' is a generic term, not a specific default user.

Model chaining in Pega requires that the parent class has a model with the same name as the child class model (a), and the child class model has 'Call Super Class Model' enabled (b). Pattern inheritance (c) is a different inheritance mechanism and is not required for model chaining.

When Conditions in Pega are rules that evaluate to true or false and can be used in Activities, Sections, Flow actions, and Harnesses to control conditional behavior. They cannot be directly referenced within Property rules, as Properties are data definitions that don't support conditional logic references.

In Pega, the cover object (which groups related work objects) is stored on the clipboard in a standard system page named pyWorkCover. This is a reserved clipboard page name that follows Pega's naming convention where system pages start with 'py'.

In Pega's clipboard architecture, objects stored in temporary memory during processing are called 'pages'. The clipboard is the overall storage mechanism, Embed pages are nested page structures, and Work Objects are persisted business cases - but the temporary memory object itself is called a page.