Skip to main content

Creating higher ruleset versions by skimming rules

Pega Community logo

Note: The following content, referenced from Pega Community, is included here to help you better achieve the module learning objectives.

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.

You can select between two types of skimming, a minor skim and a major skim. The minor skim moves rules to a higher minor version of your application, for example, after you implement new enhancements. You can check the minor ruleset version by analyzing the middle two digits of the ruleset version. An example of a minor skim is skimming rules in 06-05-01 through 06-09-25 into the 06-10-01 ruleset versions. The major skim moves rules into a higher major version of your application, such as a new release. The two first digits in the ruleset version correspond with the major version. A major skim is skimming rules 06-05-01 through 06-09-25 into the 07-01-01 ruleset versions.
Before you begin:
  • Check in all the rules that you want to skim. For more information, see Checking in a rule.
  • To ensure that users cannot edit lower versions of the ruleset after skimming, secure the lower ruleset versions. For more information, see Security tab on the Activity form.

During skimming, the system copies rules to a new ruleset with a higher version number. The rules in the lower versions remain unchanged in your system.

  1. In the header of Dev Studio, click Configure System Refactor RuleSets .

  2. On the RuleSets tab, in the Refactor Rulesets Utilities section, click Skim a Ruleset.

  3. In the Skim to create a higher version window, define the skimming settings:

    Choices Actions
    Perform a major skim
    1. Select the Major Version RuleSet Skim radio button.

    2. In the RuleSet list, select a ruleset that you want to skim.

    3. In the From Major Version list, select an existing major version that you want to skim to a higher version.

    4. In the To New Version field, enter a ruleset version that you want to create with skimming.

      Ensure that the new version relates to the skimming type.

      For example: If you want to perform a major skim on the 06-09-25 version, enter 07-01-01.
    5. Click Skim.

    Perform a minor skim
    1. Select the Minor Version RuleSet Skim radio button.

    2. In the RuleSet list, select a ruleset that you want to skim.

    3. In the Starting Version and Ending Version lists, select a version range of the ruleset that you want to skim.

      For example: Select 06-05-01 as a start version and 06-09-25 as an end version.
    4. In the To New Version field, enter a ruleset version that you want to create with skimming.

      Ensure that the new version relates to the skimming type.

      For example: If you want to perform a minor skim on the 06-05-01 to 06-09-25 version range, enter 06-10-0.
    5. Click Skim.

    Note: The window displays the progress and the results of the skim after the process is complete.
  4. If any errors occur, click the Total Errors link.

    You can only access the list of errors from the Skim to create a higher version window.

Note:
  • Research and resolve errors that occurred during the skim operation.
  • Update access groups or application rules to make the new major version available to appropriate users. For more information, see Learning about access groups.
  • To ensure that users can edit only the highest ruleset version, secure lower ruleset versions. For more information, see Security tab on the Activity form.
  • To decrease the number of rules in your system and speed up rule resolution, delete rules in the lower major versions. For more information, see Deleting a ruleset.
    Note: Ensure that your organization accepts deleting rules that are no longer in use.

  • Organizing rules into rulesets

    To identify, store, and manage the set of rules that define the reusable elements of an application, organize rules into rulesets. When you group rules into a ruleset, you save time, because you can reuse an entire ruleset within different applications in your system instead of reusing or creating individual rules.

  • Creating rulesets

    Reduce development time and costs by creating rulesets. After you create rulesets, you can group rules, which are reusable elements of your application, in a logical way. As a result, you can conveniently manage, maintain, and reuse your rules.

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice