Application Data Records
Data Objects are defined by a collection of fields. During Case processing, the fields associated with Data Objects are given values. The values can be provided by user input, an external data source, or an event, like a background processing task. The unique collection of fields and values for a single instance of the Data Object is called a Data Record. Each Data Record is stored in a system of record, whether stored locally in the Pega database or externally in a system of record maintained by the client organization.
Data Records and Data Objects
Data Objects represent key business entities. Data Objects contain all the fields that are necessary to describe the object they represent. For example, the First name, Last name, Full name, Email, and Phone fields are used to describe a customer, so these fields are stored in a Customer Data Object. Data Records associated with a Data Object consist of values for each of the fields that describe the object. The Data Records for the Customer Data Object could consist of values like Ian, Mitchell, Ian Mitchell, [email protected], and 111-222-3333. Data Objects define the fields and their permissible values, limiting the input values to valid options while reducing errors, and streamlining the workflow.
Generally, a change to a Data Record does not require a change to the business process itself. For example, adding or updating a customer does not change how the business handles customer data. A change to the fields stored within the Customer Data Object does represent a change in the way the business handles information. A business that wants to add service subscription levels to their offerings might add a Subscription level field and require all new customers to select a subscription upon account creation.
Using a Travel application as an example, an Airport Data Object is associated with a Case Type. Each airport is defined by a code, city, and country. Together, these values describe a single airport and represent one Data Record. Because airport information remains consistent across all Cases, storing this information as Data Records ensures data consistency and reuse.
Data Records can be selected from a list using an identifying field. Once a record is selected, additional information associated with that record is displayed. In this example, selecting an airport code updates the displayed city and country values:
Local data storage
Data Records provide a way to store reference data within a Data Object. This data can be entered and maintained as part of the application and reused across Cases, ensuring consistency without direct access to a database.
Match the numbers to the following image to learn more about Data Records stored locally in a Data Object:
1. Unique key: Each Data Object includes a field that uniquely identifies each Data Record. This unique key distinguishes one record from another. In the Airport Data Object, the ID field identifies each airport using an airport code, ensuring that every airport record is uniquely defined.
2. Data Records: After a local data source is established, Data Records can be added to store reference information. For example, the Airport Data Object can contain a Data Record for each airport location, with values such as ID, city, and country.
Note: Each Data Record stored locally includes a system‑generated unique identifier called pyGUID. When a Data Record is created, the application automatically assigns a unique value to this identifier. The identifier value is stored with the Case, allowing the associated Data Record to be referenced and retrieved later as needed.
External data storage
A Data Object can also reference information maintained outside the application, such as data stored in an external system or service. In this scenario, each set of external values represents a Data Record. At run time, Data Pages associated with the Data Object are used to access the external source and supply values for the fields defined in the Data Object. For example, an online grocery delivery application uses Data Pages to retrieve product information from a supermarket’s external product database and display a list of available items for customers to order.
Note: Data Pages are data structures that provide access to information defined by a Data Object. A Data Page can represent a single Data Record or a list of Data Records, using the fields defined in the Data Object. Data Pages make data available to the application when needed and allow the same data to be reused, helping improve efficiency and consistency. For more information on Data Pages, see Data Pages overview.
Check your knowledge with the following interaction:
This Topic is available in the following Module:
If you are having problems with your training, please review the Pega Academy Support FAQs.
Want to help us improve this content?