Data object tables
The initial Pega Platform database schema has database tables that contain rows corresponding to instances of concrete Data- classes.
Operator ID
The
pr_operators
table contains rows that correspond to instances of the
Data-Admin-Operator-ID
class.
As a best practice, retain Operator ID records permanently. Do not delete rows that correspond to former operators. You can change the operator password to prevent anyone from logging on, and can mark the operator as unavailable for work.
Listener and related data instances
The
pi_data_connect
table is associated with the
Data-Admin-Connect-
class. Instances of the classes derived from this
class support service listeners and related interface data.
For example, JMS listeners are instances of the Data-Admin-Connect-JMSListener class.
Administrative data instances
The
pr_data_admin
table holds instances of classes derived from the
Data-Admin-
class, excluding those explicitly mapped to other tables:
- Operators
- Instances of classes derived from Data-Admin-Connect-
- Instances of classes derived from Data-Admin-DB-.
For example instances of the
Data-Admin-System-Settings
class are
mapped to the
pr_data_admin
table.
Data-UniqueID instances
The
pc_data_uniqueid
table corresponds to the
Data-UniqueID
class, and contains a single row for each work item ID
format in use. This row records the most recently assigned work item ID of that format,
usually computed by a stored procedure.
For example, if the most recent purchase order is PO-4253, then when the next purchase order is entered, the value of the pyLastReservedID property increments to 4254.
Work item attachments
Attachments to work items are instances of concrete classes derived from the
Data-WorkAttach-
class. In the initial
Pega Platform
database schema, this class is linked to the
pc_data_workattach
table.
(However, the attachment itself is included for content or Enterprise Content Managment
(ECM) attachments, which are saved in an external document repository and are accessed using
Connect CMIS rules.)
Instances of the Data-WorkAttach-File class may contain an uploaded file of any type, up to 1 Gigabyte in initial size, which is converted to text, if necessary, using Base64 encoding. Instances of the Data-WorkAttach-ScanDocument and Data-WorkAttach-ScreenShot classes both contain images, which are also converted using Base64 encoding.
Database, database table, and class group instances
Instances of these three
Data-
classes are associated with the
pr4_base
table:
- Data-Admin-DB-Table
- Data-Admin-DB-Name
- Data-Admin-DB-ClassGroup
These are known as foundation classes.
Automated Unit Testing results
Instances of two
Data-
classes that support the use of features of
Automated Unit Testing are associated with the
pr_data_autotest
table:
- Data-AutoTest-Result-Case
- Data-AutoTest-Result-Suite
Content Images
Instances of the
Data-Content-Image
class are associated with the
pr_data_file
table. See
About Image Content data instances.
Other data instances
When you create a data table by using the Data Table wizard, you can optionally cause instances of the data table class to be stored in a new database table. This choice simplifies future migration of the contents of the database table if necessary, and can improve performance and facilitate reporting on data table contents. Typically, the data table class is derived from the Data- base class and the new table is named pr_zzzzz, where zzzzz is the class name.
The
pr_data
table holds instances of any concrete class derived from the
Data-
base class not covered by the tables listed in this topic. For
example, (as initially configured during installation) the
Data-Party-Com,
Data-Party-Person
and
Data-Corr-Email
classes map to this table.
The
pr_data
table has only a few exposed columns. As a best practice for
good performance, configure your
Pega Platform
database so that classes
with a high volume of saved instances or activities are not mapped to this table.
A few
Data-
classes (for example
Data-RuleSearch
and
Data-Work-Summary
) are mapped to the
pr_data
table
but do not correspond to any rows of that table. These classes are the Applies To class of
specialized reports that access various database tables using custom getContent activities.
Running the reports does not access the
pr_data
table.