Working with the PegaRULES database
System tables

 Working with the PegaRULES database

In the initial PegaRULES database schema, certain PegaRULES database tables contain instances of concrete classes derived from the System- base class.

CautionDo not alter the mapping, schema, or structure of these tables unless advised by Pegasystems support staff.

Table

Description
pr_page_store

Contains rows corresponding to instances of the System-SavedPages class.

When a user session times out, the system saves a user's entire thread context automatically in this table until that user completes a log-in challenge or an expiration timeout occurs.

The system automatically deletes rows of this table that are more than three days old.
pr_portal_state

Contains instances of the classes Pega-Portal-Developer and Pega-Portal-User, which store saved information about portal use by each connected user.
pr4_rule_sysgen

Contains instances of the System-CachedConclusion class.
pr_sys_appcache_dep

Supports operations in AppCache mode.

See Understanding Application-Based Assembly mode.

pr_sys_appcache_entry

Supports operations in AppCache mode.

See Understanding Application-Based Assembly mode.

pr_sys_appcache_shortcut

Supports operations in AppCache mode.

See Understanding Application-Based Assembly mode.

pr_sys_app_ruleset_index

Contains instances of the System-ApplicationRuleSetIndex class, which relates RuleSet versions to applications that reference those RuleSet versions.

pr_sys_app_hierarchy_flat

Contains instances of the System-Application-Hierarchy-Flat class, which contains the "Application built-on" list for each application.
pr_sys_cache_dep

Supports rules assembly cache operations when running in Rules Assembly cache mode, which is a previous generation caching technology for legacy applications using the deprecated Override rulesets.

See Understanding Application-Based Assembly mode.
pr_sys_cache_entry

Supports rules assembly cache operations when running in Rules Assembly cache mode, which is a previous generation caching technology for legacy applications using the deprecated Override rulesets.

See Understanding Application-Based Assembly mode.
pr_sys_cache_impl

Supports rules assembly cache operations when running in Rules Assembly cache mode, which is a previous generation caching technology for legacy applications using the deprecated Override rulesets.

See Understanding Application-Based Assembly mode.
pr_sys_class_ancestors

Contains instances of the Data-Rule-ClassAncestor class, which supports rule resolution.
pr_sys_context

Contains rows corresponding to instances of the System-Requestor-Context class, which is used for passivated requestors.
pr_sys_decchg

Contains rows corresponding to instances of the System-Declare-Changes class, which is used to support execution of declarative expression rules.

pr_sys_locks

Contains rows corresponding to locks held, which are instances of the System-Locks class.
pr_sys_queues

Contains rows for queued service requests from concrete classes, such as System-Queue-DefaultEntry, which are derived from the System-Queue- abstract class (except for classes explicitly mapped to another table).
pr_sys_queue_autotest

Contains rows for queued unit test suite runs, which are instances of the System-Queue-TestSuite class.

pr_sys_queue_execreq_conn

Contains rows for queued connector requests, which are instances of concrete classes derived from the System-Queue-ExecutionRequest-Service- class.

See About Connector Request Processor data instances.

pr_sys_queue_execreq_svc

Contains rows for queued service requests, which are instances of concrete classes derived from the System-Queue-ExecutionRequest-Connect- class.

See About Service Request Processor data instances.

pr_sys_queue_sla

Contains rows for instances of the System-Queue-ServiceLevel class, which support event-driven processing of service-level agreement deadlines and goals by the Pega-ProCom agent.

See Understanding the Pega-ProCom agent.

pr_sys_queue_startflows

Contains rows for starter flows, which are reflected in instances of the System-Queue-StartingFlows class.

Facilitates fast operation of the drop-down list of starting flows by application on application portals.

pr_sys_rule_impl

Contains rows for VTable.

pr_sys_ruleset_index

Contains rows for the System-RuleSet-Index class, which support improved performance by providing quick access to RuleSet list has codes.

pr_sys_statusnodes

Contains one row for each participating node in the system, which correspond to instances of the System-Status-Nodes class.
This table occasionally can contain duplicate rows. This is because the true key is based on an encrypted form of the node name, the system name, and the path of the temporary directory.

Run the RemoveOldNodes activity to purge rows corresponding to nodes that have been inactive for at least 24 hours.

pr_sys_updatescache

Contains one row for each change to the rules since the most recent pulse processing by the PegaRULES agent. These rows correspond to instances of the System-Updates-Cache class.

When rules are updated and added to the cache, this table is scanned by a trigger, and the table is emptied when cache processing completes.

See Understanding the PegaRULES agent.
pr_sys_workindexer_queue

Contains rows of the System-Work-Index class, which identify work items that need re-indexing for full-text search.
pr_sys_user

Contains one row for each rule delegation, which correspond to instances of the System-User-MyRules class.
pr_sysjobs

Contains rows for queued column population jobs, which are instances of the System-Job-PropertyOptimization class reported on the Column Population Jobs tab of the Database landing page.

See System category — Database landing page.

 

Definitions passivation, referencing rules, timeouts
Standard rules Atlas — Initial Database Table data instances
Atlas — Standard classes derived from the System- base class

HomeWorking with the PegaRULES database

Open topic with navigation