Personal RuleSet

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

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

Personal RuleSets are used in with the check-out and check-in features, part of the rule check-out facility. They are also used with the private check-out and private check-in features. When an application developer checks out a rule (using either the standard check out or private check out), it enters his personal RuleSet.

A personal RuleSet is always topmost in a user's RuleSet list. Rules in a personal 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 personal RuleSet. The maximum size of this cache (for all developers combined) is determined by elements in the fua node of the prconfig.xml file or by Dynamic System Settings.

To report on checked-out rules, create a report type of rule (report definition, list view, or summary view) with Data-Rule-Locking as the Applies To class. Create this rule using the rule form for the appropriate report type or using the V5 Report Wizard (Rule Locking data source).

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

	check in, check out, rule check-out facility, rule cache
	About RuleSet rules Understanding checkout and your personal RuleSet Working with the Show Checked Out display and Bulk Check-in

Definitions — P