- 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 and a ruleset version
For easier maintenance and development of your application, create rulesets so that you can categorize the rules that your application uses based on usage, purpose, and dependencies. You can also create newer versions of existing rulesets to keep track of version control. As a result, you can quickly locate and analyze the elements that you change in your application.
- Configuring ruleset version settings
For improved management of your application, define the behavior of your ruleset and how it interacts with other elements of your application by configuring ruleset version settings.
- Copying rulesets
To speed up application development, reuse resources by copying rulesets. For example, you can copy a ruleset if you want to modify only some of the rules that the ruleset includes, to increase flexibility of your application.