More about RuleSet and RuleSet Version rules

When effective

After you save a RuleSet 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.

Controlling use of updated rules

If a rule is added to a new, higher version of a RuleSet, it may be instantly available to others who have RuleSet lists that allow access.

For example: assume that a user RuleSet list references version ALPHA:04-06, and a rule named GAMMA in ALPHA:04-06-03 is added to override the lower version in ALPHA:04-06-02.

The next time this user session retrieves GAMMA, this user accesses the updated 04-06-03 version. Other users may access the older version.

For work objects, the associated flow rule is retrieved at each task boundary (each shape). Thus corrections and enhancements to a flow rule (through higher versions) can affect assignments and work in progress.

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. Select > System > Tools > Refactor RuleSets > Copy/Move/Merge RuleSet to start the tool. See About the RuleSet Maintenance wizard.

Skimming RuleSet versions

When you use the Skim tool, Process Commander automatically creates a new RuleSet version rule instance corresponding to the next major version above the current version. For example, if you skim a RuleSet version 03-14-07, it creates RuleSet version 04-01-01. Select >Tools > Refactor RuleSets > Skim a RuleSet > Skim a RuleSet to start a skim operation.

Deleting RuleSets and versions

Use the RuleSet Delete tool to delete RuleSets or versions. Select > System > Tools > Refactor RuleSets > Delete a RuleSet to start the tool. If there are no rules associated with a RuleSet or a version, you can delete them on the Versions tab.

Useful standard functions

The Pega-RULES Utilities library contains these

• 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 following call  is true if Alpha:04-07-15 is a prerequisite of Beta:01-06-07 PROJ-942

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

RuleSets for delegated rules

To allow updates, delegated rules in a production application must belong to unlocked RuleSet versions. For added security, you can copy the delegated rules into a single, dedicated, and unlocked RuleSet and version, and then lock other RuleSet versions. CLINIC 7/15/05

No check out, always available

Update RuleSet and RuleSet version rules carefully. Note these special conditions:

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

Rule types with no version

The following rule types do not use RuleSet versions:

• Class — Has a version for export and migration purposes only.
• Application
• RuleSet
• RuleSet Version
• Access of Role to Object
• Access Deny
• Library

	check in, check out, delegated rules, private RuleSet, rule management facility, Archive tools, major version, Preflight check, skim
	About the RuleSet Delete tool About RuleSet Version rules About the RuleSet Maintenance wizard
	Atlas — Standard RuleSet Names

About RuleSet rules