The database that contains the standards — every one of the occasions of solid classes got from the Rule-base class — is known as the PegaRULES database. This database is likewise once in a while distinguished as the rulebase, yet it contains more than rules.
Classes that are mapped to the PegaRULES database are known as interior classes. Solid classes that relate to lines of an outer database are known as outside classes.
Rather than the diligent occasions of tenets and different protests in the PegaRULES database, cases on a client clipboard are impermanent. At the point when a client logs off, the framework erases the client's clipboard.
On the off chance that the framework spares an occasion from the clipboard into the
Pega RULES database, the spared duplicate stays after the client who made it logs off, and is accessible to different clients. Along these lines, the PegaRULES database contains the persevering objects of Process Commander.
Through the database table and database information examples, Process Commander designers working with database executives figure out which classes of articles are put away into which database tables.
Despite the fact that the PegaRULES database is at times called a rulebase, don't confound the word rulebase — a physical accumulation of principles and different questions in a social database — with the Rule-base class, a dynamic class that has no cases.
Working with the PegaRULES database:
- The PegaRULES database, as at first introduced, comprises of around 100 tables that hold every one of the guidelines, information occurrences, work things, history, and other solid articles from interior classes of your Process Commander framework. Perspectives, records and put away methodology bolster execution and other preparing prerequisites.
- By definition, outside classes relate to tables in different databases. These tables are not some portion of the PegaRULES database.
- A database executive can change and advance the PegaRULES database to meet arrangement, security, execution, and detailing necessities.
- When at first introduced, V6.2SP2 contains around 100 database table (Data-Admin-DB-Table) information cases, connected to around 105 database tables and 7 sees in the PegaRULES database.
- For instance, the database table case namedData-Admin-Operator-ID is connected to the pr_operators social table. The database table occasion namedData-Admin-references an alternate social table pr_data, a catch-all table that contains columns for examples of solid classes got from Data-that are not contained in different tables.
- This table records the PegaRULES database tables and a case of a solid class that maps to that table. No classes are at first mapped to the pr_other table, the default get all table for occasions of classes not unequivocally mapped.