Table of Contents

Rule skimming for higher ruleset versions


Only available versions of this content are shown in the dropdown

Skimming is an operation of copying rules from your rulesets into a ruleset of a higher version. Skimming improves the performance of your application because the system filters out rules that are unavailable for rule resolution. Because the new ruleset contains only the highest rule versions, skimming simplifies rule resolution and minimizes the rule data that you ship to a different version of your application.

Skimming collects the highest version of every rule in the ruleset and copies the rules to a new major or minor version of that ruleset on the same system. Rule availability and the type of skimming determine which rules the system carries to a higher ruleset version.

You can select between a major skim and a minor skim. The skim type corresponds with the digits in a ruleset version number. The two first digits define the major version, and the two middle digits define the minor version. For example, in the ruleset version 06-09-10, 06 indicates the major version, and 09 corresponds with the minor version. The major ruleset version typically specifies a release of your application or other significant changes, while the minor version relates to an enhancement or a less extensive change in your application. When you select a skim type, consider changes that you want to merge in the higher ruleset version. The final two digits correspond with patch releases and do not have a separate skim type associated with them. Skimming copies rules so that all your rules in lower ruleset versions remain unchanged. During skimming, the system omits rules in the major versions that are lower than the major version that you specify. For example, if you opt to skim 02-05-02 into 03-01-01, the system ignores any rules in the version 01-XX-XX.

The following table displays which rules you can include in a higher ruleset version by using either the major or minor skimming type:

Skim type/Rule availability Available Not Available Final Withdrawn Blocked
Major Yes No Yes No Yes
Minor Yes No Yes Yes Yes

The update history of the new skimmed rule contains only one instance that reflects the date and time of the rule creation based on the skim operation. The history of the source rule is available and remains unchanged.

  • Creating higher ruleset versions by skimming rules

    Improve the performance of your application and simplify the rule resolution by skimming rules to create higher version rulesets. Skimming filters out rules that are not available for rule resolution and makes rule management more convenient.

Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.