Pega PRPC Rules and Architecture

The options "Whenever used", "When used if no value present", and "When used if property is missing" all represent backward chaining strategies where calculation is triggered by property retrieval. Conversely, "Whenever inputs change" is a forward chaining strategy where calculations are pushed automatically as soon as source values update.

Activities cannot be called by expressions in a way that tracks property changes. While decision trees, decision tables, and map values can be executed within declare expressions to support automatic change tracking, activities are procedural and do not support Pega's automatic declarative dependency tracking.

This statement is false because backward chaining only calculates values when they are explicitly requested. If a property is rarely accessed, backward chaining performs better than forward chaining, which recalculates values every time an input changes, potentially causing unnecessary overhead.

Draft flows can be executed and are useful for demonstration or testing purposes before finalizing a flow. The other options are incorrect because draft flows are executable and participate in rule resolution like regular flows.

Declare Expressions, Edit Validate, and When rules are declarative or decision rules in Pega. They support the "Build for Change" philosophy by externalizing business rules and calculations from procedural code, making them easy to update. Rule-File-Text is simply a static file container and does not directly support this design principle.

Class pollution refers to the practice of creating custom rules directly in high-level classes like Work- rather than in specific subclass levels. This clutters the inheritance hierarchy and makes rule navigation and maintenance difficult. Improper subclassing or excessive rules in specific application classes do not define this concept.

This statement is false because the standard work party rule provided by Pega is named Default, not Requestor. While applications can define custom work parties like Customer or Requestor, there is no system requirement or standard rule always named Requestor created for every application.

This statement is false because the Class Explorer in Pega is a standard development navigation tool. It is accessible to all developers, business analysts, and users who have developer access to the portal (such as Dev Studio), not just system architects and system administrators.

In Pega, the interest page is another term for the primary page. It represents the clipboard page that is currently the main focus of execution or processing for a rule or activity. Secondary, parameter, and local pages serve different purposes, such as passing parameters or holding temporary helper data.

The tools.getLockManager().isLocked() method checks lock status without attempting to acquire the lock, making it ideal for this diagnostic purpose. The other options either require acquiring locks or use inefficient database queries.

In Pega's rule resolution process, rulesets are assembled from various data sources. The ruleset order within a source is preserved by appending the top-most ruleset from a data source to the top of the accumulated ruleset list. Distractors incorrectly state that it is appended to the bottom or that order is not maintained.

Pega’s official guardrails guide developers to build robust, maintainable applications. Core guardrails include establishing a robust foundation, designing intent-driven processing, and building for change. While event-driven concepts exist in software architecture, Design Event Driven Processing is not defined as a standard Pega guardrail.

In Pega, the New harness is used to initialize and create a new case. Once the case is submitted and created, the user is transitioned to the Perform harness to complete the initial assignment. Review and Confirm harnesses are for read-only viewing or confirmation of completed work, respectively.

External systems access Process Commander data using Services (such as SOAP or REST) or the Snapstart URL interface to initiate or open cases. Since both are inbound integration methods, either is correct, whereas Connectors are outbound.

The pxProcess page contains node-wide, system-level details initialized at startup. Requestor pages contain session-specific data, thread pages isolate execution tasks, and user pages store user-created data structures on the clipboard.

Rules of the Rule-Service-Email class define how PRPC receives and processes incoming email messages as services. Data-Email-Account stores authentication and connection configurations for sending/receiving email rather than processing logic.

The availability status of a rule, such as Yes, Blocked, Final, or Withdrawn, is stored in the standard metadata property pyRuleAvailable. Properties like pyRuleStatus or pyRuleBlocked do not store the primary availability configuration.

A Declarative Expression automatically computes and updates a property's value dynamically whenever any of its input properties change. Models initialize values, Constraints validate conditions, and Formulas are components rather than rule types.

The with directive in Pega HTML/XML code sets the active context to a different clipboard page for the duration of the tag's scope. Directives like literal, comment, and when serve formatting, commenting, and conditional logic.