Skimming

<<Back

·         Skimming allows a developer to copy the rules of multiple ruleset version to next highest rule set version.

·         Skimming is of two types

1)      Major Skimming

2)      Minor Skimming.

·         Major Skimming means the new rule set version created will be updated with its major version value.

·         Minor Skimming means the new rule set version created will be updated with its minor version value.

·         Skimming filters the duplicate rules from the lower versions

·         The patch version of new skimmed rule set version number will be ’01’ by default.

·         Skimming drops the duplicate rules. For example, if you move a ruleset containing rules with ruleset versions 01-01-01, 01-01-02 and 01-01-03 into a new target ruleset and specify a version of 01-02-01, the target ruleset version will contain the highest version of all the source rules contained in versions 01-01-01, 01-01-02 and 01-01-03 with lower-versioned duplicates dropped.

·         In this example, if a rule is duplicated in both 01-01-01 and 01-01-02, the rule will be moved from 01-01-02 to the new ruleset name with ruleset version 01-02-01, and the duplicate rule in 01-01-01 will be dropped.

·         Select the Designer Studio> System >Refactor > Rule Sets

Major Skim:

·         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.

·         Skimming rules in 06-05-01 through 06-09-25 into 07-01-01

Minor Skim:

·         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.

Skimming rules in 06-05-01 through 06-09-25 into 06-10-01