Pega Process Commander (PRPC) - Classes, Rules & Inheritance

In Pega, every class must specify a direct parent class through Direct Inheritance, which is mandatory. Pattern Inheritance is optional and uses naming patterns to find parents automatically. Therefore Direct Inheritance is the required component.

Trigger rules in Pega are declarative rules that automatically execute processing when specific database operations occur. They can be configured to run on save (create), update, or delete operations, making 'All of the above' the correct answer.

Pattern Inheritance works by removing trailing characters (hyphens, numbers) from class names to find parent classes. For 'MICO-Finance-', removing the trailing hyphen gives 'MICO-Finance'. The dash is part of the pattern, not the base name.

Rule-Declare-Constraints is used to enforce conditions that must always be true. The statement 'ActualExpense never greater than BudgetExpense' describes a constraint - a rule that enforces a business condition across all cases. This rule type continuously validates and prevents violations.

When rules (Rule-Declare-When) evaluate conditions and return only Boolean true/false results. Decision tables, trees, and maps can return various values - strings, numbers, or other data types. Only When rules are restricted to Boolean outputs.

Class hierarchies are commonly visualized using outlines (indented text lists) and tree diagrams (graphical representations with branches). Flow charts show processes, not hierarchy. Comments and documentation are for explanation, not structure visualization.

The Top-Down Approach establishes abstract classes at higher levels to store properties and rules that apply to multiple leaf classes below them. This promotes reuse and consistent behavior across related classes. Cross-Class Approach is not a standard Pega term.

In Pega, the class that corresponds in name to a class group is known as the container class (or class group container class). It maps directly to the class group data instance Data-Admin-DB-ClassGroup.

In Pega, abstract classes cannot create work objects and end with a hyphen. 'PegaRP-Work-Object-Admin-' ends with a hyphen, indicating it's abstract. 'PegaRP-Work-Object-Admin' and others without hyphens are concrete classes that can create instances.

The correct sequence starts with the base, then creates Work classes hierarchically (IV→V→VI→VII→VIII) before Data classes (II→III). This establishes the work structure first, then data structures. Option B follows this pattern correctly.

Pega can create classes derived from base classes like Work-, Data-, Link-, Assign-, and Index-. Since both Link- (a) and Assign- (b) are valid base classes, option 'd' is the correct stored answer.

Process Commander's Declarative Model automates decisions about when processing should occur. Unlike HTML fragments or decision trees/tables which require explicit calls, declarative rules run automatically based on events and conditions.

In Pega's rule naming convention, Harness rules are named 'Rule-HTML-Harness'. The naming follows the pattern Rule-{Type}-{Specific}. Option A correctly identifies the full rule type name.

Local variables in Pega are activity-specific. They exist only during the execution of that activity and are not stored persistently. They are not stored on the clipboard as temporary variables (A), cannot be stored in the database (C), and are not stored in automatically created named pages (D). Their scope is strictly limited to the activity context.

Agent rules in Pega define background processing tasks. They specify the trigger or wake-up intervals (how often the agent runs) and the specific activities to execute upon wake-up to perform the background work, making all options correct.

Pega's best practice for flow design recommends limiting each flow shell to approximately 10 Assignment or Processing shapes. This promotes modular, maintainable process design. Five shapes (A) is unnecessarily restrictive, while 15 (C) or 20 (D) shapes per shell make flows overly complex and harder to debug and maintain.

For short to medium-sized lists that change frequently, Field Value (B) is the appropriate choice in the TableEdit tab. Field Values allow easy modification of list options through simple rule updates rather than code changes. Local List (A) is for static lists, Remote List (C) is for external data sources, and Prompt List (D) serves different dynamic selection purposes.

SmartBuild follows a logical top-down creation sequence: first, define the Class Structure, then define the Properties associated with the classes, followed by the User Interface to display or input these properties, and finally the Activities containing business logic.