More about RuleSet Version rules

When effective

After you save a RuleSet Version 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 Version form affected only those requestors who logged in after the change. Active requestors were not affected.

Before locking a version

As a best practice, use the Preflight tool before locking a version of a RuleSet, and research each warning message, eliminating those you can. Also, choose View > Rules > All Checkouts and review the resulting report to confirm that no rules from that RuleSet version are checked out.

Choosing the version number

Every RuleSet normally has at least one version numbered 01-01-01. Create additional versions for developers who make enhancements and fixes to rules in the RuleSet.

• For enhancements, developers need a version in which the middle two digits are incremented. This is known as a minor version.
• For bug fixes, developers need a version in which the last two digits are incremented. This is known as a patch version.
• For major releases, developers need a version in which the first two digits are incremented. This is known as a major version. Major versions can be created automatically during skim operations rather than through the rule form.

You can use any increment between numbers. For example, you can create version 01-01-10 without creating 01-01-02.

As developers work, they may request that you create more RuleSet versions and lock (that is, mark as secure) a RuleSet version for which development is complete.

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.

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.

No check out, always available

Update RuleSet version rules carefully. Note these special considerations:

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

Skim operation

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 > Rule Management > Skim a RuleSet to start a skim operation.

Deleting a RuleSet Version

. Use the RuleSet Delete tool to delete both the rules in the RuleSet and the RuleSet Version rule. Select Tools > Rule Management > Delete a RuleSet to start the tool.

You can use the Delete toolbar button () delete a RuleSet version that contains no rules. However, this is not advisable when the RuleSet itself is marked as secure, with a password in the To Update a Rule-RuleSet Version field. (You can't delete a RuleSet version that contains rules.)

Renaming and moving a RuleSet Version

Use the RuleSet Maintenance to move (rename) or copy a RuleSet Version. Select Tools > Rule Management > Copy/Move RuleSet.

Version locking exceptions

Locking a RuleSet version (by selecting the Lock this Version box) affects all but two rule types. Locking does not prevent later changes to application rules or class rules associated with the RuleSet.

Rule types with no version

Some rule types are not versioned:

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

 

	Archive tools, major version, Preflight check, skim
	How the system finds rules through rule resolution About the RuleSet Delete tool About the RuleSet Maintenance wizard

About RuleSet Version rules