The initial Pega Platform database schema has database tables that contain rows corresponding to instances of concrete Data- classes.
table contains rows that correspond to instances of the
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
table is associated with the
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
table holds instances of classes derived from the
class, excluding those explicitly mapped to other tables:
- Instances of classes derived from Data-Admin-Connect-
- Instances of classes derived from Data-Admin-DB-.
For example instances of the
mapped to the
table corresponds to the
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
class. In the initial
database schema, this class is linked to the
(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
classes are associated with the
These are known as foundation classes.
Automated Unit Testing results
Instances of two
classes that support the use of features of
Automated Unit Testing are associated with the
Instances of the
class are associated with the
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 and the new table is named pr_zzzzz, where zzzzz is the class name.
table holds instances of any concrete class derived from the
base class not covered by the tables listed in this topic. For
example, (as initially configured during installation) the
classes map to this table.
table has only a few exposed columns. As a best practice for
good performance, configure your
database so that classes
with a high volume of saved instances or activities are not mapped to this table.
classes (for example
) are mapped to the
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