Pega PRPC Platform Fundamentals

Access Groups in Pega define the application, portal layout, and security roles accessible to a group of users who perform similar job functions. They do not represent the entire business structure or the individual developers, but rather map operators to specific application permissions.

In Pega, the Obj-List method creates a top-level clipboard page of class Code-Pega-List to hold the search results. The actual instances returned by the query are stored inside the pxResults page list embedded within this Code-Pega-List page.

A business user is the person who uses the application to receive, process, and resolve work items. They are the end-users who interact with the work baskets and assignments. Business managers oversee users, process architects design the flows, system architects design the technical architecture, and system administrators maintain the infrastructure.

The Process Commander organization hierarchy is built on three nested levels: organization (highest), division (middle), and unit (lowest). This structure allows for granular control of work assignment, access controls, and organizational reporting. Options B, C, and D either use wrong terminology ('company' instead of organization) or wrong levels (work group and user are not hierarchy levels).

In Pega, text file rules (Rule-File-Text) store static content like CSS style sheets, JavaScript files, or images. These rules are cached and served directly by the web server, bypass rule resolution during execution, and optimize performance compared to dynamic HTML fragments or harnesses.

Application Accelerator in Pegasystems PRPC is a framework generation tool that creates basic application structures like class groups, rulesets, work parties, work object forms, and organizational elements (workbaskets, worklists, workgroups). However, communication and integration capabilities with external systems require manual configuration using connectors, services, and integration-specific rules that are beyond the scope of the basic framework generation.

SmartBuild Step 10 focuses on adding communication capabilities to applications, with correspondence being the primary feature implemented - the ability to generate and manage correspondence documents and communications.

In Pega and similar BPM systems, operator roles and access permissions are specified within Access Groups. Access Groups control which operators can access which applications and rulesets.

Best practices in flow design recommend limiting Assignment and Processing shapes to approximately 15 per flow shell to maintain readability and manageability of the process flow.

In Pega's rule hierarchy, section rules are Rule-HTML-Section type. They contain HTML and markup to define reusable user interface sections that can be included in harnesses and other sections.

When looping through a page list in Pega, special subscript keywords allow referencing specific pages. () points to the first page, () to the last page, and () allows adding pages at the end during iteration. However, () is not a valid index reference in this context - there is no built-in () subscript for page lists during looping.

In Pega PRPC, organizations are created as instances of the Data-Admin-Organization class. This class defines organizational structure and settings. Upon installation, PRPC includes a default organization named 'pega.com' - this is the out-of-the-box organization that serves as the initial organizational context in the system.

Text File rules in Pega are specifically designed to store static content like HTML style sheets (CSS files) and JavaScript code. Unlike most Pega rules, Text File rules are not subject to rule resolution - the system does not search through multiple RuleSets or versions to find them. Fragments, Streams, and Harness rules are all subject to standard rule resolution mechanisms.

Rule-File-Binary is the Pega rule type designed to store binary file content, including images like JPG, JPEG files, GIFs, and other non-text files. Rule-File-Text stores text-based files, while Rule-Obj-Binary and Rule-Obj-Text are not valid Pega rule class names for file storage purposes.

In Pega, properties can be aggregate (containing multiple values) or single-value. Page, PageList, PageGroup, ValueList, and ValueGroup are all aggregate property types - they can hold multiple values or nested structures. SingleValue is NOT an aggregate property - it holds exactly one scalar value like a string, number, or date, making it the correct answer for what is NOT an aggregate property.

A Local Flow Action in Pega allows a user to perform additional actions on an assignment without completing it. In this scenario, the HR Manager needs to attach a budget sheet before approving - this is an additional action that doesn't complete the assignment. Local Flow Actions are perfect for such requirements like attaching documents, adding comments, or updating information while keeping the assignment open. Rule-Template-Excel instances are for Excel templates, Correspondence Rules are for communications, and Connector Flow Actions relate to external integrations.

The Requestor Page is a special clipboard page in Pega that maintains session-level information for each user requestor (session). It stores critical runtime information including the user's access roles and privileges, the RuleSet list (determining which rules are available to the user), and HTTP protocol parameters. Process Page, Thread Page, and User Pages are not the correct names for this system clipboard page.

When an Assignment shape uses the 'Worklist' standard rule, it expects assignments to go to a user's worklist. However, if the Router uses 'ToWorkbasket', it tries to route the assignment to a workbasket instead. This creates a conflict - the assignment shape expects individual user assignment but the router sends it to a queue. This incompatibility causes the flow to be suspended, and Pega transfers control to the FlowProblems flow to handle the error condition.

Router, Notify, and Utility shapes in Pega flows are all based on the Rule-Obj-Activity rule type. These are technically specialized flow shapes that internally invoke activities. In the Security tab of an Activity rule, you can see that Router, Notify, and Utility are all listed as activity-based rule types. They are not separate rule types from Rule-Obj-Activity - they are specialized implementations that use activities as their foundation.

In Pega, subscripts can be numeric or non-numeric. Page Groups use non-numeric string keys as subscripts to identify and reference specific pages within the group. For example, you might have a Page Group with keys like 'PolicyA', 'PolicyB', etc. Page Lists and Value Lists use numeric subscripts (1, 2, 3...). Java Objects are not a Pega property type that uses subscripts in this context.