Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Creating rulesets

Updated on April 5, 2022

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

For example, you can create a ruleset that stores service-level agreements (SLAs), and a separate ruleset for case notifications. If you want to make any changes to the SLA ruleset, your modifications are granular and you avoid the risk of unintended changes occurring in the case notifications ruleset. You can also provide a way for members of your development team to work in isolated sandboxes by creating branch rulesets.
When you create new rulesets, consider the following guidelines:
  • Create a new ruleset with a top-level class that inherits directly from @baseclass.
  • Use names that are easy to remember and unique for each ruleset.
  • Use names that clearly convey the purpose of the ruleset; avoid using acronyms that might be difficult to decode. For example, name your ruleset UPlusTelcoContracts instead of UPTC.
  • Always begin your ruleset name with a phrase that clearly identifies your company and the business purpose. This convention also prevents potential ruleset conflicts.
  • Do not use Pega or Pega- as a prefix for your ruleset names. These prefixes are restricted to Pega Platform internal use and can cause unexpected behavior.
  • The maximum length of a ruleset name is 32 characters. Avoid using spaces in ruleset names.
  • Avoid the use of special characters such as dashes (-), underscores (_), plus signs (+), or quotes (“ ”). The system does not permit the saving of rules with these attributes.
  • For more information about using patterns for the ruleset version number, see Organizing rules into rulesets.
  • Creating a ruleset version

    Create a new version of an existing ruleset or create a new ruleset with an associated ruleset version.

  • Completing the Save As RuleSet form

    You can use the Save As RuleSet form to copy a ruleset. The system copies the values in the Security, Category, and History tabs. The version is the one you specify in this form.

  • Creating branch rulesets

    You create branch rulesets in the Branch area on the Application rule's Definition tab. When branching a ruleset, the non-branch ruleset's Validation mode is used by the branch.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us