More about RuleSet Name rules

Rule management

Use the Security tab on the RuleSet Name form to specify whether you want this RuleSet to use the rules management facility. This facility requires users to check out rules before they can change the rule. Changes affect only a personal copy of the checked-out rule.

This facility provides extra security regarding who can change rules in a RuleSet, and prevents possible problems from two or more users who attempting to change one rule at the same time.

If rules management is in effect, the Check in () and Check out () buttons appear in the toolbar for rules in the RuleSet of most types. The Save button () does not appear until a rule is checked out.

When effective

After you save a RuleSets form, active requestor sessions on the current node that are associated with that access group are immediately updated. Requestors at other nodes in a cluster are updated when the next system pulse occurs on their node.

In Version 4, changes to a RuleSet form affected only those requestors who logged in after the change. Active requestors were not affected.

Deleting RuleSets

You don't need to delete a RuleSet to prevent its use. Update access groups on your system so that none of the access groups reference the RuleSet.

You cannot delete a RuleSet Name rule when an associated RuleSet version exists. First delete all the rules in all versions, then delete the RuleSet versions, before deleting the RuleSet. Or, use the Delete RuleSet tool. See About the RuleSet Delete tool.

Renaming and merging two RuleSets

Use the Copy function of the RuleSet Maintenance wizard to rename a RuleSet, or to merge two or more RuleSets into a new one. See About the RuleSet Maintenance wizard.

Useful standard functions

The in the Pega-RULES Utilities library contains these helpful functions:

• Call the standard function rule IsInRuleSetList() to test whether a RuleSet is included in your own requestor RuleSet list.
• Call the standard function rule isRuleSetInDependencyPath(A, B) to test whether one RuleSet is dependent upon another through pre-requisites, where A and B are RuleSet names or RuleSet Versions. (If you omit the versions, the highest version is assumed.) For example, the call

IsRuleSetInDependencyPath("Alpha:04-07-15","Beta:01-06-07")

         is true if Alpha:04-07-15 is a prerequisite of Beta:01-06-07.

RuleSets for delegated rules

If your application in production includes delegated rules, these must belong to an unlocked RuleSet version, to allow updates. For added security, you can copy the delegated rules into a single, dedicated, and unlocked RuleSet and version, and then lock other RuleSet versions.

No check out, always available

Change RuleSet Name rules carefully. Note these special conditions:

• Check-out () and Restore () operations are not available for these rules.
• RuleSet Name rules are always available. You cannot change the availability of a RuleSet Name rule to No/Draft Mode, Blocked, Withdrawn or Final.

	check in, check out, delegated rules, private RuleSet, rule management facility
	About the RuleSet Delete tool
	Atlas — Standard RuleSet Names

About RuleSet rules