Pega PRPC Fundamentals

Split-Join is the Pega flow shape that allows you to split processing into two or more independent secondary flows that operate in parallel. Each parallel flow executes independently, and the parent flow waits for all parallel flows to complete before continuing. Split-For-Each is for iterating over a list, Called Flow is for invoking another flow sequentially, and SpinOff Flow is for asynchronous processing without waiting.

In Pega's access control inheritance model, when an access role is specified at a parent class level, it automatically applies to that parent class AND all its child classes throughout the class hierarchy. This cascading inheritance ensures consistent permissions across related classes. However, if a child class has an explicit access rule that overrides the inherited role, the child's specific rule takes precedence for that class.

The standard organizational hierarchy in Pega, from top to bottom, consists of Organization (top level), Division (middle level), and Unit (bottom level).

Work IDs in Pega follow specific patterns: W- is a valid prefix format, W-TCS shows organization prefix, and TCS-W- shows alternate format. All of these are valid Work ID formats that Pega can generate and process. The key is that Work IDs must be unique identifiers that follow configurable prefix patterns, often including organization codes.

Pega property types starting with pz are protected system properties that cannot be modified. Properties starting with px are standard Pega properties that can be modified, and py properties are also editable. The pz prefix designation is specifically reserved for locked, read-only system properties that maintain platform integrity.

pxUrgencyWork uses the Rule-Declare-Expressions rule type to calculate its value using the @ formula shown. Decision tables use Rule-Declare-DecisionTable, triggers use Rule-Declare-Trigger, and OnChange rules use Rule-Declare-OnChange. The @ formula syntax with functions like @100 and @max is specifically used in Declare Expressions rules for property calculations.

Page Context in Pega defines the scope of where an action or rule will apply - specifically, it targets the properties of the page defined in that context. $Any and $None are special page list keywords, not directly related to Page Context definition. Page Context is not limited to declarative rules and can be used in various rule types to specify the target page.

In Pega's class hierarchy, ordinary work objects inherit from the Work-Object- base class, making option B true. Covered work objects inherit from Work-Cover- class, not Cover-Object-. Folders can contain multiple covered work objects, and folders themselves are typically organizing structures rather than work objects.

By default, assignments in Pega use harness rules associated with the Perform action. This is the standard harness displayed when users work on assignments. New, Confirm, and Review are other harness types used for different purposes (creating new work, confirming completion, or reviewing existing work).

A WorkPool in Pega is a collection of similar Work Objects grouped together for organizational and routing purposes. It allows related work items to be managed collectively. WorkGroups are collections of users, not work objects. ClassGroup refers to Pega class groups, which is a different concept entirely.

Work Objects are created when a flow is opened, typically through the Starting flow process. This initialization happens in Opening Flows (option A). Primary flows, secondary flows, and sub flows are all types of flows that might be used during processing, but the actual creation of the work object occurs during the opening/starting phase.

The HTML property type in Pega is used for customizing display by allowing rich HTML content to be embedded in sections and harnesses. It enables developers to add custom HTML markup, styling, and formatting to enhance the user interface beyond standard property displays. It is not specifically for XML pages, adding HTML screens as separate entities, or just for special HTML characters.

Declare rules in PRPC execute at multiple points: as flow processing advances between tasks, after activity step methods complete but before transitions, and when objects are committed to the database. This makes them versatile for maintaining data integrity throughout the application lifecycle.

The Integrator shape in PRPC flows is specifically designed for bi-directional communication with external systems. It enables receiving data via services and sending data via connectors, acting as the gateway for all external system interactions.

The Property-Set method is the standard way to update property values in activity steps. It efficiently sets property values without requiring direct Java code. Option B's AtSetValue is incorrect, and Option A's Java method is not the recommended approach in PRPC.

Rule-RuleSet-Version is the only rule type among the options that can be locked and unlocked. This prevents changes to rules in that version, maintaining stability. RuleSet names, lists, and other components don't have this lock/unlock capability.

PRPC class names have a maximum length of 64 characters. This is a platform constraint that developers must adhere to when naming classes. Neither 32 characters, 128 characters, nor unlimited length are correct.

For frequently changing short-to-medium lists, Field Value should be specified in the TableEdit tab. Field Values are designed for dynamic list management that changes often, unlike Local Lists or Prompt Lists which are more static.