Object-Oriented Programming

In Pega, every class MUST have a Direct Inheritance specified - it is mandatory. Direct Inheritance defines which class the new class immediately extends (its parent class in the class hierarchy). Pattern Inheritance is optional and only applies if the class name follows pattern conventions. Option B is correct because without Direct Inheritance, a class cannot be created. Option A is not mandatory, option C is incorrect (only Direct Inheritance is required), and option D contradicts the requirement.

In PEGA, ordinary work objects inherit from the Work- base class (patterned as Work-Object- in class naming). Covered work objects do not use a separate 'Cover-Object-' class - they are work objects that have a cover relationship with another work object. Folders can contain multiple covered work objects, not just one, and folders themselves are not work objects.

Model chaining in Pega requires that the parent class has a model with the same name as the child class model (a), and the child class model has 'Call Super Class Model' enabled (b). Pattern inheritance (c) is a different inheritance mechanism and is not required for model chaining.

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.

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.

Model chaining in Pega DOES override properties in child classes with properties from parent class models. Option B states it doesn't override, which is the false statement the question seeks. Options A, C, and D describe actual behaviors of model chaining.

In a Pega Data Model (or Declare Expressions / Model rules like Data Transforms), property initialization can be defined using property references in value fields, literal values, calling functions, or boolean expressions. Property-Set is an activity method, not a model rule initialization option.

Data-Operator-Party is Pega's standard class for representing operator parties, including originators. The naming pattern follows Pega's class hierarchy convention. Options B, C, and D use incorrect class naming patterns that don't follow Pega conventions.

Foo b = a.clone() is correct because calling clone() creates a new object with the same contents as the original. Foo b = a (A) only copies the reference, not the object itself. Foo b; b=a (C) is the same as A. Option D is invalid.

In Pega PRPC, the pyDefault model is the standard model provided for most concrete classes. It contains default properties and behaviors. pyStandard is not a standard model name, and the other options (pyDefModel, pyStdModel) are not standard Pega model names.

Rule-File-Binary is the Pega rule type designed to store binary file content such as images (JPG, JPEG), PDFs, and other non-text files. Rule-File-Text is for text files, while Rule-Obj-Binary and Rule-Obj-Text are not standard Pega rule types for file storage.

The Obj-List method returns results in a clipboard page of class Code-Pega-List. This is a standard Pega list class, not Rule-Pega-Obj (used for rule instances) or pxResults (a page name, not a class).

For a RuleSet with 5 versions, Rule-RuleSet-Name has 1 instance (one name entry) while Rule-RuleSet-Version has 5 instances (one per version like 01-01, 01-02, etc.). The name is shared across versions.

Not all classes require direct inheritance. Pattern inheritance and directed inheritance can be used separately. @baseclass is the root and has no inheritance, but other classes can inherit through patterns without direct parent specification.