Skimming is the act of taking the highest version of a rule and saving it into a new, higher ruleset version. As a result, it applies mainly to rule resolved rules, and there are exceptions to what gets skimmed based on the availability of the rule as well as the type of skim being performed.
Traditionally, there are two types of Skims, Major and Minor. These reflect the tri-partite naming convention for ruleset versions, Major-Minor-Patch. During a Minor skim, rules are stored in a higher Minor version, and during a Major skim, rules are stored in a higher Major version.
Major: Skimming rules in 06-05-01 through 06-09-25 into 07-01-01
Minor: Skimming rules in 06-05-01 through 06-09-25 into 06-10-01
During a major skim, rules with Availability of 'Yes', 'Blocked', and 'Final' are carried forward. Rules with availability of 'No' (not available) or 'Withdrawn' are filtered out. Blocked rules are carried forward because a Blocked rule can block rules in other rulesets, and that relationship should be maintained if it exists.
During a minor skim, rules with Availability of 'Yes', 'Blocked', 'Withdrawn' and 'Final' are carried forward. Rules with availability of 'No' (shown as 'Not Available' in the table below) are filtered out.
The following table displays which rules are carried forward, based on availability.
Available | Not Available | Final | Withdrawn | Blocked | |
---|---|---|---|---|---|
Major | Yes | No | Yes | No | Yes |
Minor | Yes | No | Yes | Yes | Yes |
To invoke the Skim tool, call on the PegaRULESMove_RunBachReq activity. This activity accepts an input parameter called mode. For general skimming, this property should be set to "skimming".