Working with the PegaRULES database Index tables

This topic describes PegaRULES database tables that support indexes. Most have table names that start with one of these values:

pr_index

pc_index

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

These standard database tables store index instances.

Table	Description
pr_index_assignmentdeps	Rows correspond to instances of the Index-AssignmentDep class, which support dependent assignment processing. See case type dependency.
pr_app_branch_idx	Rows correspond to instances of the Index-ApplicationBranch class, which relates branches of applications to the application rule containing the branch. See branch RuleSet.
pc_index_accel	Rows correspond to instances of Index-UpdateAccessUsers class, which supports the Application Profiler (see application profile).
pc_index_flowref	Rows correspond to instances of the Index-FlowRef class, which contains indexes of flows cross referenced by cover class.
pc_index_workparty	Rows correspond to instances of the Index-WorkPartyURI class. These instances support rapid lookup work items 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_index_css	Rows correspond to instances of the Index-CSS class, which associates a CSS selector with the harness, section, or flow action that includes it, for performance reasons.
pr_indexaccessgrouproles	Rows correspond to instances of the Index-AccessGroupRoles class, which allows quick access to the access roles in access groups.
pr_indexaccessgroupwkpools	Rows correspond to instances of the Index-AccessGroupWorkPools class, which allows quick access to the work pools in access groups.
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.
pr_index_circumstance-def	Rows correspond to instances of the Index-CircumstanceDefinition class, which supports searches for rules by circumstance. About Circumstance Definition rules.
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.
pr_index_operatorskills	Rows correspond to instances of the Index-OperatorSkills class, which supports skill-based routing. See More about skill rules.
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 (). See About the Referencing Rules display.
pr_index_scheduledtask	Rows correspond to instances of the Index-Pega-ScheduledTask class, which relates subscribers to scheduled report executions (work items of class Pega-ScheduledTask). See scheduled task.
pr_index_warnings	Holds instances of the Index-Warning class, containing warning messages produced upon Save or revalidate operations. Used in the Guardrails tool operations.

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

Don't confuse these tables — which contain rows automatically created and deleted by PRPC 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.

	attachment, Custom Fields, folder, Index- base class, referencing rules, timeouts, work party
	How to set up an index
	Atlas — Initial Database Table data instances Atlas — Standard classes derived from the Index- base class

Working with the PegaRULES database