Related terms
The PegaRULES database uses triggers to maintain views, and uses stored procedures to meet important integrity and consistency requirements.
Caution: Do not alter trigger elements except as advised by Pegasystems Global Services.
Database trigger names begin with the prefix TPPR_. Triggers monitor changes to the tables containing rules, and ensure that database views and the rule cache are appropriately updated when a rule is added, updated, or deleted.
Note: Do not confuse database triggers with the Rule-Declare-Trigger rule type, a Pega 7 Platform facility that executes an activity when a page is saved.
Stored procedure names begin with the prefix SPPC_.
Name |
Description |
sppc_data_uniqueid
|
Supports the computation of unique work item ID values, associated with the Data-UniqueID class. |
sppr_sys_statusnodes_set
|
Updates the status of the current node in the statusnodes table. |
sppr_sys_reservequeueitem
|
Supports asynchronous execution by agents. |
sppr_sys_reservequeueitem_b
|
Supports asynchronous execution by agents. |
sppr_sys_updatescache_add
|
Adds an entry to the pr_sys_updatescache table, which coordinates rule updates in multinode systems. |
sppr_sys_updatescache_flush
|
Removes entries in the pr_sys_updatescache table that are older than a specified number of minutes. |
sppr_sys_updatescache_gettime
|
Returns the last pulse time and the current database time. |
sppr_sys_getindextime
|
|
sppr_rr_class_filtered
|
Supports rule resolution processing. |
sppr_purge_table
|
|
sppr_aggregate_usage
|
Supports roll-up of usage statistics. |
sppr_populate_indexdata
|
Working with the PegaRULES database