A RuleSetname 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 Process Commander system to another.

On rule forms, the RuleSet name appears at the upper right.

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.

Process Commander itself consists of six standard RuleSets:

• Pega-AppDefinition — Standard rules supporting Direct Capture of Objectives features
• Pega-ProCom — Standard rules that support business process management (BPM) applications
• Pega-IntSvcs — Standard rules that support integration
• Pega-WB — Standard rules that support the portal infrastructure
• Pega-RULES — Standard rules that support business rules engine and rule resolution
• 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 private RuleSet. The system creates each private RuleSet automatically, named to match the developer's 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.

	Archive tools, Direct Capture of Objectives, organizational RuleSet, Process Simulator, private RuleSet, rule management facility, rule resolution, RuleSet list, RuleSet version, skim
	About RuleSet Name rules About the RuleSet Delete tool About the RuleSet Maintenance wizard Identifying parts of rule and data forms
	Atlas — Standard RuleSets

Definitions — R