Pega PRPC Fundamentals

Semantic versioning follows the format Major.Minor.Patch, where Major indicates incompatible API changes, Minor adds backwards-compatible functionality, and Patch fixes bugs. Options A and B reverse this standard order, while D incorrectly adds a fourth component.

In Pega's class hierarchy, @baseclass is the ultimate root class from which all classes inherit. Top-level classes directly inherit from @baseclass, while Work- and other pattern classes are specialized subclasses. Business logic resides in lower-level implementation classes, not top-level structural ones.

The statement about concrete classes requiring class groups is not universally true. While Work-derived concrete classes need class groups for database mapping, Data- classes and other concrete class types do not. Classes ending in "-" are abstract by convention, and abstract classes indeed should not have instances.

Embed- classes are designed specifically to be embedded within work objects and cannot exist as independent pages. Data- classes can be saved as pages. The key distinction is that Embed- objects exist only as part of their parent work object and are not separately persisted to the database.

In Pega, both Covers and Folders are specialized types of work objects that inherit from the Work- base class. They are stored as instances in the database and have all the fundamental properties of work objects, including status tracking and pyID assignment.

Covers have automatic resolution behavior - when all work objects covered by a Cover reach Resolved status (not necessarily Resolved-Complete), the Cover automatically resolves to Resolved status. This is built-in Cover functionality in Pega.

Folders can contain any combination of Work Objects, other Folders, or Covers. This hierarchical structure allows nested organization of work items. Options A and B are too restrictive, while D incorrectly denies all containment possibilities.

A Folder can contain multiple items, and each item can belong to multiple Folders simultaneously. This many-to-many relationship is fundamental to Pega's folder structure, allowing flexible categorization where a work object can appear in different folders without duplication.

A class group enables multiple concrete classes with a common key format to share a single database table. This optimizes storage and supports reporting across related classes. Class groups are directly related to reporting requirements in Pega applications.

This appears to be about a form/workflow system (possibly Pega or similar). In such systems, the Subscriber Enrollment text is typically defined in the Short Description of the Flow, as the Flow controls the process including enrollment. The Harness is about UI presentation, and Class Groups are about organization, not enrollment text.

This question appears to be about a form/workflow system (possibly Pega). When users need to select multiple automobiles, this requires a property type that can store multiple pages of data. Page List is the correct type for storing multiple instances (multiple automobile records), while Value Group/List store single values and Page Group is for organizing related pages, not multiple selections.

This question is about a form/workflow system implementation choice. When you have 4-5 regions that don't change frequently, a Prompt List (static list configured in the application) is the best implementation. It's simpler than a Remote List (database query) and more appropriate than Local List or Class Key Value for this use case. A Prompt List is efficient for small, stable datasets.

Dynamic Select enables cascading dropdowns where one selection filters subsequent choices. This is standard Pega terminology for parent-child data relationships. Property-Set sets values, Dependency List defines dependencies, Obj-List retrieves data - none implement selection-based filtering.

HTML Fragments in PRPC are created using the Rule-HTML-Fragment rule type, which allows developers to create reusable HTML components that can be embedded in other rules. This rule type specifically stores HTML markup that can be referenced and included dynamically in various parts of the application.

PRPC has specific standard attachment types including File, URL, Screenshot, and Scanned Document. 'Object' is not one of the predefined attachment type categories in the PRPC platform. The standard types are designed to cover common attachment scenarios.