PRPC Rules and Configuration

The Application rule's purpose is broader than just defining RuleSets and versions - it also specifies built-on applications, application documents, and other configuration. The statement is incomplete, making it false.

Auto-generated HTML is available in Section rules and Flow Action rules. HTML Fragment and Harness rules are manually authored. HTML Property is not auto-generated in the same way - it's a specific rule type for property-level HTML.

Pega workflows allow branching or calling other flows in four main ways: Subflow (Called Flow), Spin-off (asynchronous flow execution), Split-For-Each (iteration over pages), and Split-Join (parallel execution of different flows). All listed options represent these ways.

Access groups in Pega are indeed instances of Data-Admin-Operator-AccessGroup class. This class stores access group configuration including which access roles, portals, and work pools are assigned.

Reports can be generated for Rule-, Assign-, and Data- classes in Pega. Code- classes are not reportable in the same way - they're system classes that don't have standard reporting capabilities.

All classes must have directed inheritance EXCEPT @baseclass, which is the ultimate parent and has no parent itself. Pattern inheritance applies to some classes, but directed inheritance is required for all non-root classes.

When conditions can be used in Preconditions (to control whether an activity executes) and Transitions (to control flow between steps). They are NOT used directly in step methods, parameters, or loop conditions - those use different expressions.

Quick Create supports When rules and Property rules. Decision Trees, Decision Tables, and Map Values require the full rule form and cannot be created via Quick Create.

Classes inherit table mapping from their parent class. Policy-Admin-Work maps to PC_PolAdmin table, so any class created under it (like Policy-Admin-Work-MyClass) will also map to PC_PolAdmin.

For a small, fixed set of 5 values, Local List is the correct choice in the Table Edit tab. Remote List is for external data sources, FieldValue is for dynamic lists stored in database, and ClassKey is for keyed access.

A Transition in an activity is a true-false test evaluated after each step executes that determines whether processing continues with the next step or jumps elsewhere. It's not for transferring control to another activity (that's Call), not evaluated before execution, and not automatically enabled.

Assignment smart shapes can have Assignment activity (what runs), Local action (user actions), CorrName (correspondence), and Confirmation Note (shown after completion). Router activity is not a direct property of smart shapes.

When a covered object (like a cover work object) is in a transaction, Pega creates a page named pyWorkCover to track the cover context. pyCoverPage, pyCover, and pyWorkPage are not the standard page names for this purpose.

Work classes and cover classes should be in the same rule set to maintain proper class structure and inheritance. Cover classes are used to group related work objects, and keeping them in the same rule set ensures consistent access and management.

The Organization Setup Wizard creates three standard users: WorkUser for case processing, ProcessArchitect for process design, and SystemArchitect for system configuration. These users provide the core access roles for a new organization in PRPC.

Embedded pages in PRPC cannot be nested within other embedded pages due to architectural limitations. The system does not support hierarchical embedding of pages, which prevents potential circular references and maintains predictable page structure.

When the Auto-generated HTML checkbox is re-checked, PRPC regenerates the entire HTML section, replacing any custom code that was added while the checkbox was unchecked. This is by design - auto-generation takes precedence over custom modifications to maintain consistency.

In PRPC (Pega Rules Process Commander), the standard activity NewDefaults is a placeholder (dummy activity) that can be overridden in user classes to implement pre-display logic before the harness new is shown. Static values for work objects are typically set in pyDefault.

To display a calendar icon alongside a single date value property in a perform harness, use the Date-Calendar Rule-HTML-Property. This control provides both the date display and a calendar icon for date selection in one interface element.

In PRPC, properties with the same name can exist across different classes or rule sets, but not within the same rule set and class combination. This allows for property reuse across different contexts while preventing naming conflicts within a single class.