PEGA PRPC Activities and Methods

Local Variables in programming exist only within the context of a specific activity, function, or block. They are created when that context is entered and destroyed when it exits. They are not stored on the clipboard, not automatically stored in databases, and not stored in automatically created pages. Their scope is limited to their defining context.

Pages and Classes in Pega Rules Process Commander (PRPC) activities serve multiple purposes. They link page names to specific classes, enable smart prompts to display relevant rules and properties in the activity form, and correspond to pages residing on the clipboard.

In PRPC activities, the For Each directive is specifically designed to iterate through embedded pages (page lists). Loop and Get Next are not valid PRPC directives, and For Next is not used for embedded page iteration.

The Page-New method in PRPC creates a new page on the clipboard and instantiates it. New-Page and Open-Page are not valid method names, and Page-Open would typically open an existing page rather than create a new one.

Activity-End terminates both the current activity and the calling activity, then continues with the next activity on the requestor's list. End-Activity, Exit-Activity, and Activity-Exit are not valid PRPC method names.

Activities can create work objects through multiple approaches: creating a step page of the work object's class, calling the Add activity, or specifying a starting harness. All three methods are valid ways to create work objects.

The Obj-List method creates a top-level clipboard page with class Code-Pega-List. This class contains query results. Rule-Pega-Obj is for individual rule instances, pxResults is a property name within the list page, and the class is not the same as the returned instance class.

Integration smart shapes in Pega use Connect type activities, which handle external system connections. Router is for routing work, Assign is for assignment, and Utility is for general utility tasks - none are specifically for integration.

Obj-Save has a Write-Now checkbox that writes immediately to the database, while Obj-Delete has an Immediate checkbox for the same purpose. Both bypass the normal Commit method requirement when these checkboxes are selected.

The Show-Page method displays step page information in XML format, which is useful for debugging activities. Show-XML and Show-Step-Page are not valid PRPC methods, and Show-Html would show HTML format, not XML.

Local variables in PRPC activities are scoped only to the activity's execution context. They are not stored on the clipboard, cannot be persisted to the database, and are not automatically stored in named pages - they exist temporarily during activity execution.

In PRPC activities, the For Each directive is specifically designed to iterate through embedded pages (page lists). Loop and Get Next are not valid PRPC directives, and For Next is not used for embedded page iteration.

Page-New is the correct method to create a new page in the Pega clipboard. It initializes a new page of a specified class that can then be populated with data. The other options (New-Page, Open-Page, Page-Open) are not standard Pega methods for page creation.

Activity-End is the correct Pega method that terminates the current activity and returns control to the calling activity, which then continues with the next activity on the requestor's list. This is essential for controlling flow in Pega processes. The naming convention places the object (Activity) before the action (End).

Creating a work object from a Pega activity requires multiple steps: creating a step page of the appropriate class, calling the Add activity to instantiate it, and specifying a starting harness for the UI. All three actions are necessary components of the work object creation process.

Obj-List always creates a top-level clipboard page of class Code-Pega-List, which contains the results of the database query. The pxResults mentioned in option C is actually a property within that page, not the class itself. Code-Pega-List is Pega's standard class for list-type results.

Connect activities are specifically designed for integration in Pega, handling communication with external systems through connectors, SOAP, REST, and other protocols. The Integration smart shape uses Connect activities to manage data exchange. Router, Assign, and Utility serve different purposes in flow processing.

In Pega, Obj-Save has a Write-Now checkbox that causes immediate database write, while Obj-Delete has an Immediate checkbox for the same purpose. Both bypass the standard Commit method queue and perform the database operation instantly. Remembering which method uses which checkbox name is key.