ruleset name

A ruleset name is an instance of the Rule-RuleSet-Name rule type. Each ruleset defines a major subset of rules in the PegaRULES database, because every instance of every rule type references or "belongs to" a ruleset. A ruleset name is a major aspect in:

Access control
Grouping interrelated rules
Managing the rules
Moving applications (sets of rules) from one system to another.

The term ruleset sometimes refers to the name instance and sometimes informally refers to the contents of that ruleset— all the instances of Rule- classes associated with that ruleset.

The Rule-.pyRuleSet property, present in every rule instance, records the ruleset name to which the instance belongs.

Pega 7 Platform consists of several standard rulesets, including these:

Pega-AppDefinition — Direct Capture of Objectives features
Pega-AutoTest — Automated Unit Testing support
Pega-Desktop — Designer Studio
Pega-EndUserUI — HTML and JSP generation
Pega-Engine — Foundation
Pega-Gadgets — Designer Studio
Pega-ImportExport — ZIP archive support
Pega-IntegrationArchitect — Rule forms
Pega-IntegrationEngine — Integration runtime
Pega-IntSvcs — Integration
Pega-ProcessArchitect — Rule forms
Pega-ProcessEngine — Process rules runtime
Pega-ProCom — Business process management (BPM) applications
Pega-Reporting — Reports
Pega-RuleRefactoring — Ruleset management
Pega-RULES — Business rules engine and rule resolution
Pega-RulesEngine — Foundation
Pega-UIDesign — User interface facilities
Pega-UIEngine — User interface runtime facilities
Pega-WB — Portal infrastructure
CheckInCandidates — Optional. Empty, used by rule check-in processing. Version 01-01-01 is not locked.

Any application developer who can check out rules has a personal ruleset. The system creates each personal ruleset automatically, named to match the Operator ID value.

A ruleset name is limited to 64 characters. The property pyRuleSet, included in most rule types, identifies the ruleset for that rule.

Related terms

Open topic with navigation