PEGA PRPC Platform Fundamentals

In Pega harness types, the Review harness is Read-Only by design. It allows users to view case data without making modifications. New and Perform harnesses allow editing, Reopen reactivates closed work, and Confirm is for final approvals.

The Decision shape in Pega flows can reference Map Value, Map Value Pair, and Decision Table rules for evaluating conditions and routing. When Rule is used in a separate shape specifically for rule-based branching, not directly in the Decision shape for routing logic.

In Pega flows, a Delay shape represents a repeated pause or wait that can occur multiple times during processing. Goal is an objective, Deadline is a time limit. Delay is the shape type that can repeat.

PRPC does use the W- prefix for work objects by default, but organizations can and do configure their own meaningful prefixes to match their business processes. The statement claims prefixes cannot be customized, which is false.

Step page is not mandatory in each step of an activity. Many steps operate on the primary page or explicitly specify pages. Step page is optional and used when you need to work with a specific page in the clipboard.

Rule-Declare-OnChange is specifically designed in Pega to run activities automatically whenever the value of a specified property changes. Rule-Declare-Index is for improving database query performance, Rule-Declare-Constraints defines validation rules, and Rule-Declare-Trigger executes activities when objects are created, updated, or deleted - not specifically for property value changes.

In Pega, a flow can have only one end shape. This is by design - flows represent a single business process with a defined termination point. Having multiple end shapes would create ambiguity about which path the process actually took. If you need multiple possible outcomes, you should use different end statuses on the same end shape or use decision shapes to route to appropriate processing before reaching the single end.

Rule Resolution in Pega is the mechanism that selects the best rule to execute based on factors like class hierarchy, rule set availability, circumstance, and other criteria. It applies to rule types that can have multiple versions targeting different contexts, like Declare-OnChange, Declare-Constraints, Declare-Trigger. Rule-HTML-Property is a UI rule that defines how a property is displayed and is selected directly by its class and rule set - it does not participate in rule resolution.

In Pega PRPC, standard local actions are predefined actions available on cases. AttachANote, AttacAURL (note: typo in original), and AttachAFile are all standard local actions that allow users to add notes, links, and files to a case. AttachADocument is not a standard local action in this context.

In Pega, the Group By option is available in the Summary View, not in the List View. Summary View provides aggregation and grouping capabilities that allow users to organize and summarize data based on specified fields, whereas List View displays individual records without grouping functionality.

The Tracer tool in Pega is used for debugging and troubleshooting processes. It allows developers to trace execution flow and inspect parameter values, clipboard contents, and other runtime information. Clipboard is for storing data, Performance tool monitors system performance, and Rules Inspector shows rule details.

In Pega router activities, the AssignTo parameter is used to specify the assignment or routing destination. SendTo is not a standard parameter in router activities. Router activities control how work is routed to different users or work queues based on business logic.

In Pega, property names with the 'py' prefix indicate standard properties that are part of the Pega platform and can be updated through user input. Other prefixes like 'px' are reserved for Pega internal use, 'pz' for inherited properties, and 'ps' for specialized purposes.

A single folder can contain multiple items, but each item typically resides in one primary folder location. This defines a classic one-to-many relationship.

Concrete classes in Pega are classes from which instances can be created (option A is correct). They must have direct inheritance (a parent class) but are not required to have pattern inheritance (option C is correct). Pattern inheritance is optional for concrete classes, so they need not have it (making C correct, not B). Option D is incorrect because they must have at least direct inheritance.

For node-scoped declarative pages, you must explicitly specify which access group(s) can load the declare page instance by entering them in the declare page rule form. This creates explicit scoping at the node level rather than relying on organization/division rulesets or the current user's access group, which apply at broader scopes.

In Pega, the Class Group (work pool) container is responsible for defining the key structure (typically pyID) and mapping instantiated work objects of its member classes to a single database table. 'Work-' and '.@baseclass' are base classes, not key definitions.

Integrator shapes support multiple activity types beyond just 'Connect', including 'Router', 'Decision', 'Utility', 'Notification', and others. The restriction to only 'Connect' activity is incorrect - Integrator is a versatile shape that can call various activity types depending on the integration pattern and requirements.

Property-Map-ValuePair is the correct property mode for setting a property value based on a two-dimensional map value rule. It maps input properties (rows and columns) to corresponding values in a two-dimensional table structure. Property-Map-DecisionTable and Property-Map-DecisionTree are different modes for decision-based mapping, while Property-Map-Value is for one-dimensional map rules.

The Newdefaults activity (with 's') is automatically executed when a work object is created, initializing properties with default values. This is a framework-provided activity that runs as part of the object creation process. 'Newdefault' is a common misspelling, and PyDefault is a different mechanism for property initialization.