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