Data Modeling and Properties Flashcards
7 cards from real CPSA practice questions. Tap to flip, then mark Knew It or Still Learning โ missed cards come back until you master them.
Read the first 7 Data Modeling and Properties flashcards as text
In Pega's class hierarchy, what is the purpose of a Data class (classes with the 'Data-' prefix convention)?
Answer: To model business entities that exist independently of cases, such as Customer or Product
Data classes model standalone business entities like Customer or Product that are independent of any specific work case.
A developer needs to model a 'LineItem' entity that only exists within the context of an Order case and has no independent lifecycle. Which approach is most appropriate?
Answer: Embed a Page List property using an embedded data class defined under the Order class
An embedded data class used within a Page List property is ideal for child entities like line items that only exist within their parent work object.
Which class layer in Pega is recommended for storing enterprise-wide data definitions shared across multiple applications?
Answer: Organization layer
The Organization layer is the highest application layer and is appropriate for enterprise-wide shared data definitions used across all applications.
A Pega application has a class 'MyApp-Work-Order'. To which built-in base class does this work class ultimately inherit?
Answer: Work-
All work object classes in Pega inherit from the built-in base class Work-, which provides standard work properties and behaviors.
When should a developer use a 'derived' property rather than a stored property?
Answer: When the value can always be computed from other available data at runtime
Derived properties calculate their value dynamically at runtime from other data, avoiding redundant storage when the value can always be recomputed.
A developer adds a new property to the 'Work-' base class. What is the risk of this action?
Answer: It could impact all applications on the system that inherit from Work-
Modifying the Work- base class affects every application and work class inheriting from it across the entire Pega installation.
What is the recommended way to represent a one-to-many relationship between an Order and its multiple ShippingAddresses in a Pega data model?
Answer: A Page List property containing embedded ShippingAddress pages
A Page List property holds an ordered collection of embedded pages, which is the standard Pega pattern for one-to-many relationships.