web technology Online Quiz - 78

Split-Join is the correct flow shape in PRPC for parallel processing - it splits a single flow into multiple independent sub-flows that execute concurrently, then rejoins them. Split-For-Each processes items sequentially, Called Flow invokes another flow synchronously, and SpinOff Flow creates independent child flows.

A Rule-Declare-Trigger is executed automatically by the Pega engine when an instance of a specified class is saved (inserted/updated) or deleted in the database, making all of the database events trigger sources.

Declare rules in Pega (like Declare Expressions, Constraints, OnChange, and Triggers) execute automatically based on their configuration: during forward/backward chaining as control advances, after activity steps before transitions, or upon database commits.

SmartBuild in PRPC follows a specific development sequence: Class Structure first (define data model), then Properties (define attributes), then User Interface (build screens), and finally Activities (add automation). This sequence ensures data exists before UI references it, and UI exists before business logic manipulates it.

Page Context in PRPC rules specifies which page's properties the rule will operate on. It's not about excluding actions (A), not specifically about $Any/$None usage (B), and not limited to declarative rules (D). The Page Context directly targets the property scope.

The Integrator shape in PRPC flows is specifically designed for sending and receiving data from external systems. Ticket is for case processing, Fork branches flow execution, and Split-Join handles parallel processing - only Integrator manages external system communication.

Rule-Obj-When (when rules) in PRPC map to Fork shapes in flows because when rules evaluate conditions and branch flow execution accordingly. Decision and Logic aren't standard PRPC flow shapes, and Ticket is for case processing, not conditional branching.

Pega HTML rules use a custom comment syntax with curly braces: {COMMENT} text {/COMMENT}. This is not standard HTML (which uses ), but specific to Pega's HTML rule format. The other options show incorrect syntaxes (* line *, // Comment) that aren't valid in Pega HTML.

In PRPC, assignment shapes in flows include a property that references a harness rule, which defaults to 'Perform' harness. This harness displays the assignment for user interaction. New, Confirm, and Review are other harness types but not the default for assignments.

A WorkPool in PRPC is a collection of similar Work Objects that can be processed together, often for routing and reporting purposes. It's not a collection of WorkGroups (A) or ClassGroups (C). WorkPools group business objects by type or category.

PRPC defines all three roles: Process Architect (designs business processes), System Administrator (manages infrastructure and access), and System Architect (builds application structure). Therefore 'All of the above' is correct - all are standard PRPC roles.

The System Architect role in PRPC primarily works with Properties - defining data models, property types, and data structure. Process Architects design flows, System Administrators manage harness/security, and Correspondence is handled by other roles. Properties are the System Architect's core focus.

In PEGA, ordinary work objects inherit from the Work- base class (patterned as Work-Object- in class naming). Covered work objects do not use a separate 'Cover-Object-' class - they are work objects that have a cover relationship with another work object. Folders can contain multiple covered work objects, not just one, and folders themselves are not work objects.

The pxRequestor page is a standard PEGA page that contains information about the current requestor (user or system). pxUserIdentifier is a property on this page that holds the user's identifier. Other properties like pxFlowInsKey and pxAssignmentKey are found on different pages (pyWorkPage and clipboard pages respectively), and pyID is the ID property for work objects.

In PEGA, the 'New' selection list in the Process Work gadget is automatically populated with flows that have the 'Creates a New Work Object' setting enabled. When you create a new flow and check this option, it automatically appears in the New list. You do not need to manually update HTML or modify work classes for this.

The pxUrgencyWork property uses a decision tree or expression to calculate urgency. The formula shown uses AtTheRate() which is a PEGA expression function used in Rule-Declare-Expressions. Decision tables use different syntax, triggers respond to events, and OnChange rules detect property changes - none of these fit the formula shown.

When creating a ListView to display operator information (Full Names and User Identifiers), the Data-Admin-Operator-ID class is the correct 'Applies To' class because it contains the operator ID records with these properties. Rule-Obj-Operator is an obsolete class, Rule-Obj-ListView is for defining list views themselves, and Rule-Access-Role-Name contains access roles not operator data.

In PEGA, pyWorkCover is the conventional name for the page that contains a covering work object (also called a cover work object). The pyWorkPage contains the primary work object, and pyObjectCover/pyObjectWork are not standard PEGA page names.

Property-Map-Value passes a single row input to a Rule-Obj-MapValue, while Property-Map-ValuePair passes both a row input and a column input. The 'Pair' in the name refers to the two-dimensional lookup (row + column), not multiple row inputs or calling the rule twice.