Working with the PegaRULES database — Views and Indexes

Two views support reporting on work objects with open assignments. (For reporting directly on assignments, see Tables for assignments.) As a single work object may be part of multiple simultaneous flow executions, it may have more than one assignment outstanding.

If you extend the initial PegaRULES database scheme to store work object in a new table other than the default pc_work table, also adjust these view definitions to include the new table.

The pcv4_work_history table is associated with the Data-Work-History class, and provides a consolidated means to reporting on work object history across all applications and work pools. The sort order of this view is:

• pxHistoryForReference — Formed from the class group name, a space, and the work object ID, for example PEGASAMPLE W-4532
• pxTimeCreated — Date and time the history instance was saved

This sequence causes all the history instances for a work object to appear in sequence. This view is not used in standard reports. (For reporting directly on work object history, see Tables for History.)

Five views support searching and reporting on rules:

View	Description
pwbv4_circumstance_duplicates	Associated with the Data-Circumstance-Duplicates class. It supports the report on Circumstance Property Issues, available in the Rule Reports area of the Monitor Activity slice.
pwbv4_rule_locking	Associated with the Data-Rule-Locking class. It contains a row for each rule checked out by a developer, and supports reporting on checked-out rules.
pwbv4_rule_overrides	Associated with the Data-Rule-Overrides class. (This view is used only in releases prior to 4.2SP5).
pr4_rule_vw	A materialized database view, populated by triggers and associated with the Data-Rule-Summary class. It provides access to the information in all the rule tables, allowing rapid rule searches by visible key (pxInsName column). This view also supports the Advanced Find tool (left panel) and reports in the Rule Reports area of the Monitor Activity slice. In this view, the pyClass column — not the usual pxObjClass column — identifies the Process Commander class of a row. See How to report on rules of multiple types.
pwbv4_rule_summary	This view supports special rule reporting on personal development systems only. In Version 5.1 and later systems, the pr4_rule_vw view replaces this view.

Database indexes provide fast alternate access to rows of tables.

When initially installed, V5.5 contains just over 100 database indexes. Many indexes that provide fast access to rule information using alternate (secondary) keys; these indexes have low or zero turnover (adds and deletes) in a production system. Other indexes support system operations such as locking and usage tracking, and may have high turnover.

For example, the database index flow_pyClassName associates flow rule names to Work- classes, and changes only when flows are added or deleted.

Don't confuse database indexes with instances of concrete classes derived from the Index- base class. The purpose and function of both mechanisms are similar, but database indexes are supported by database software.

Index- objects, created by Declare Index rules (Rule-Declare-Index rule type), support application-specific access. For information on the tables supporint Index- objects, see Working with the PegaRULES database - Link and Index tables.