Users who have the Allow Rule Check Out? check box (on their Operator ID instance) selected can place copies of rule instances into a privateRuleSet. The name of this RuleSet is the same as their Operator ID, such as [email protected].

The system creates a private RuleSet automatically when needed. No instance of the Rule-RuleSet-Name class exists for a private RuleSet.

Private RuleSets are used in with check-in and check-out, part of the rule management facility. When an application developer checks out a rule, it enters his private RuleSet.

A private RuleSet is always topmost in a user's RuleSet list. Rules in a private RuleSet are never executed by other users.

To identify the original RuleSet and version that a checked-out rule belongs to, expand the top section of the rule form. Click the Checked out from link to open that rule.

As you develop rules, a memory cache similar to, but separate from, the rule cache contains rules in your private RuleSet. The maximum size of this cache (for all developers combined) is determined by elements in the fua node of the prconfig.xml file.

To report on checked-out rules, create a list view or summary view rule with Data-Rule-Locking as the Applies To class. Create this rule using the list view or summary view rule form; you can't use the Report wizard for this.

The private RuleSet is sometimes called the personal RuleSet. On the requestor page, the standard property pxRequestor.pxSecuritySnapshot.pxPersonalRuleSetName identifies the private RuleSet; if this is blank, the requestor cannot check out rules.

	check in, check out, rule management facility, rule cache
	About RuleSet Name rules Working with checkout and your private RuleSet Working with the Checked Out by Me report

Definitions — P