Back Forward Working with the PegaRULES database
Link and Index tables

Working with the PegaRULES database

Show all 

This topic describes PegaRULES database tables with names that start with one of these values:

  pr_index pr_link
  pc_index pc_link

Tables for Index- instances

Instances of concrete classes derived from the Index- base class support reporting and rapid data access. These instances are created and deleted by Declare Index rules.

Eight standard database tables can store index instances.

Table

Description

pc_index_accel Rows correspond to instances of Index-UpdateAccessUsers class, which supports the Application Profile wizard. BUG-3667
pc_index_flowref Rows correspond to instances of the Index-FlowRef class, which contains indexes of flow rules cross referenced by cover class.
pc_index_workparty Rows correspond to instances of the Index-WorkPartyURI class. These instances support rapid lookup work objects based on a party identifier such as an email address, Zip code, telephone number or account number.
pr_index Holds rows (if any) for other concrete classes derived from the Index- base class not covered by the other tables.
pr_indexaccessgrouproles Rows correspond to instances of the Index-AccessGroupRoles class, which allows quick access to the access roles in access groups. 5.5
pr_indexaccessgroupwkpools Rows correspond to instances of the Index-AccessGroupWorkPools class, which allows quick access to the work pools in access groups. 5.5
pr_indexassignmentskills Rows correspond to instances of the Index-AccessGroupAssignmentSkills class, which allows quick access the skills needed by an assignment that uses intelligent routing. 5.5
pr_index_circumstance-def Rows correspond to instances of the Index-CircumstanceDefinition class, which supports searches for rules by circumstance. About Circumstance Definition rules. PROJ-1131
pr_index_customfields Rows correspond to instances of the Index-CustomFields class, which contains instances that allow developers to search for rules with one or more custom fields. See How to select and classify rules using Custom Fields.
pr_index_info Supports communication between this system and an AES system.
pr_index_operators Rows correspond to instances of the Index-Operator class, which links operators to access groups. V6.1
pr_index_operatorskills Rows correspond to instances of the Index-OperatorSkills class, which supports skill-based routing. See More about skill rules. 5.5 TASK-2178
pr_index_reference Rows correspond to instances of the Index-Reference class, which contains instances supporting the Referencing Rules display, available from the Related Rules toolbar button (Related Rules). See About the Referencing Rules display.
pr_index_warnings Holds instances of the Index-Warning class, containing warning messages produced upon Save or revalidate operations. Used in the Preflight operations. 42SP6

The pzInsKey value for rows of these tables is formed from the properties pxInsIndexedKey, pxIndexCount, and pxIndexPurpose, in that order. The pxIndexCount property makes each row unique. This property is zero-based; the first (oldest) index instance has a pxIndexCount of 0. The pxIndexPurpose key part identifies the Declare Index rule that created the index

NoteDon't confuse these tables — which contain rows automatically created and deleted by Process Commander rules of type Rule-Declare-Index — with database indexes, defined by SQL that is maintained within the database by Oracle or other database software. Both support alternate key access to other instances (rows), but the two indexing facilities are independent and unrelated.

Tables for Link- instances

Four tables can hold instances of concrete classes derived from the Link- base class:

Table

Description

pr_link_attachment Supports the association of a work object attachment with a work object, as instances of the Link-Attachment class. Contains one row for each attachment.
pc_link_folder Supports the association of a work object with a folder, as instances of the Link-Folder class. This can be a many-to-many relation.
pr_link_usecase Supports the association of a use case rule with an activity, flow, or other rules that support the use case. Also supports the association of an Application Requirement rule with an application rule. Corresponds to the Link-Requirement and Link-UseCase classes. 5.4 See About Application Use Case rules and About Application Requirement rules.
pr_link Not used by any standard class. Default table for instances of other Link- classes.
Definitions attachment, Custom Fields, folder, Index- base class, Link- base class, referencing rules, timeouts, work party
Related topics How to set up an index
Standard rules Atlas — Initial Database Table data instances
Atlas — Standard classes derived from the Index- base class
Atlas — Standard classes derived from the Link- base class

HomeWorking with the PegaRULES database