Pega PRPC Fundamentals - 2

The Lookup directive is specifically designed to retrieve a property value from an instance that is not present on the clipboard. Unlike Reference directive which works with clipboard pages, Lookup fetches data from the database or other sources by key. Literal directive is for constant values, while Java directive is for Java code execution.

Local List is the preferred choice when restricting properties to a set of legal values where the set size is small-to-medium and changes frequently. Local Lists are easier to maintain and modify compared to Class Key values (which are more static) or Remote Lists (which require external table management). They provide good performance for dynamic value sets.

In legacy PRPC versions, the SysAdminDD portal layout provides the developer dashboard and administrative interfaces including wizards. Other options such as SysAdminDDWizard or SysAdminSP are not standard portal layouts.

Auto Generate HTML feature is NOT enabled by default in Pega. This feature automatically generates HTML for properties and must be explicitly enabled when needed. The default setting is False to provide developers control over HTML generation and prevent unintended rendering behavior.

The Pega Log Analyzer parses system, alert, and JVM garbage collection logs to assess the overall health of a deployment. PAL measures individual performance, SMA manages node configurations, and Preflight checks guardrail compliance.

WorkManagers monitor operational metrics using summary view reports. These reports are typically derived from classes inheriting from Work- to track case metrics and Assign- to analyze operator workloads and assignments.

Drill-down is a characteristic feature of Summary-View reports, allowing users to click consolidated summary metrics to view the detailed records. List-View reports show individual records directly and do not support drill-down capabilities.

An assignment shape in Pega can have a maximum of FIVE connectors emanating from it. These connectors represent different possible paths or outcomes after the assignment. This limit is part of Pega's flow design constraints to maintain manageable complexity in case flow design.

The Page-Copy method cannot copy properties to a destination page that belongs to a different class than the source page. Page-Copy requires both pages to be of the same class because it directly copies the entire page structure and properties. For cross-class copying, you would need other methods like Property-Set or clipboard page manipulation.

Edit Input rules are primarily used for CONVERSION of data from one format to another. They transform input values before they are stored or processed, such as converting text to uppercase, formatting dates, or transforming numeric values. Validation is handled by Validate rules, Authorization by Authorization rules, and Authentication by Authentication rules.

A private ruleset (used for personal checkouts) is automatically managed by the system. Crucially, no actual Rule-Ruleset-Name instance is created in the database for a private ruleset, making the statement false and therefore the correct answer.

Local Flow Actions do NOT advance the flow to the next step. Unlike regular flow actions that move the case forward, Local Flow Actions are designed for auxiliary actions that return the user to the same assignment after completion. They are used for actions like 'Save', 'Attach', or 'Cancel' that shouldn't progress the flow.

The Obj-List-View method is used in activities to execute a list view rule. It retrieves database records and optionally sorts them. Formatting and displaying are handled by the browser or user interface components, not by the database retrieval method itself.

The Requestor page (pxRequestor) is a system page created upon login that holds session-level details, including access roles, active rulesets, and HTTP protocol parameters. Thread and User pages contain application-level and context-specific data.

An assignment in Pega is an instance of either the Assign-Worklist class (when assigned to an individual operator) or the Assign-Workbasket class (when assigned to a work queue/basket). Therefore, 'Either' is correct.

Temporary work objects do not have a persistent work object ID, cannot be covered by a parent cover work object, and can be used in screen flows and regular flows. Since all statements are actually true, 'None' is the correct answer.

Pega Agent rules (specifically SLA agents running the queue processor) execute escalation activities for service rules and work objects when defined goals and deadlines are missed. Flows and external systems do not manage background escalation processing.

The WITH directive is used to define the active property reference in Pega expressions. It establishes which property becomes the primary reference point for subsequent operations. Reference directive is for referencing clipboard pages, Lookup for retrieving external data, and Save for persisting data.

HTML Fragments in Pega (Rule-HTML-Fragment) are indeed rules that are associated with and dependent on a specific class. Therefore, saying they are dependent on a class is true, meaning the false statement assertion is correct.

The Queue instruction (or Queue-Activity method) is used to start the execution of another activity asynchronously in a child thread, while Call executes it synchronously and Branch transfers control to it without returning.