Data objects organize the information that your application requires to process cases. By using data objects, you can simplify your data structure for easier reuse across interfaces.
Every data object consists of one or more fields that share the same context and function. An onboarding application, for example, might include a Courses data object that suggests orientation courses for new hires, and contains properties such as Course ID, Course Title, Department, Duration, and Description. These properties impose a structure on your data, and define what kind of course information the application requires to work successfully.
The model of a data object is different from the values that each property takes for a specific entry. In this example, the properties that make up a Course data object are not the same as the individual records that are associated with that data object, each of which represents a single course. Depending on the configuration of your data object, you can maintain records within the Pega environment, or source the records from external systems.
You can use a data object as a basis for one or more user interface views. Views act as building blocks for user interface forms, and support reuse across the application. By making use of data objects, you can reduce the number of times users need to enter the same data and improve consistency.
- Enabling run-time data object editing
Give users control over data by providing them with the tools they need to maintain up-to-date records. The record editor gadget helps your users change, add, and delete data at run time, which reduces maintenance effort and improves the usability of the application.