Create RuleSet Version form fields

Select an existing ruleset, or enter a Ruleset Name value starting with a letter and containing only letters, numbers, and hyphens. Ruleset names must be unique system-wide.

Give your ruleset a name that helps you manage and identify its contents. Start the ruleset name with a letter and use only letters, numbers, and hyphens. Choose names that are short and easy to remember.

An initial portion of the name can represent your company and the second portion can represent the application content or purpose. For example, you might use your company stock ticker symbol followed by letters that represent the purpose of the application or its content.

Special cases

To create a language-specific ruleset name, enter the base ruleset name followed by an underscore and the locale code. For example, enter ALPHA_fr for a French language ruleset to override text elements in the ALPHA ruleset. See Internationalization and localization — Concepts and terms.

Rule resolution

To avoid circularity, rule resolution does not apply to ruleset rules.

Restrictions

The following restrictions apply:

• Don't choose a name that starts with the four letters Pega, or other variations of this text with different case. Such RuleSets have special capabilities and are reserved for use by Pegasystems.
• Ruleset names may be up to 64 characters long, but normally are less than twenty characters long. See System limits and maximums.

When you enter a new ruleset name, the system enters a default three-part version identifier of 01-01-01. You can modify this value using another three-part identifier.

When you select an existing ruleset name, the system increments its highest version by one patch number.

Every ruleset normally has at least one version numbered 01-01-01. Create additional versions for developers who make enhancements and fixes to rules in the ruleset.

• For enhancements, developers need a version in which the middle two digits are incremented. This is known as a minor version.
• For bug fixes, developers need a version in which the last two digits are incremented. This is known as a patch version.
• For major releases, developers need a version in which the first two digits are incremented. This is known as a major version. Major versions can be created automatically during skim operations rather than through the rule form.

You can use any increment between numbers. For example, you can create version 01-01-10 without creating 01-01-02.

Rule resolution

To avoid circularity, rule resolution does not apply to ruleset version rules. A ruleset version is a rule contained in a ruleset. For example, the ruleset version 01-17-04 of RuleSet Alpha is among the other versions rules contained in the ruleset.

When you enter or select a ruleset name, the system enters a unique two-part short description comprising the name and the default version. For example, if you enter a ruleset name MyCo, the default description is MyCo:01-01-01. If you change the Version value, the Description field updates the version number automatically. You can edit this field to suit your requirements.

If the Application Validation (AV) mode of ruleset validation is not enabled, a new ruleset version must have at least one prerequisite. When you enter a ruleset name, the system enters in this field the highest Pega-ProcessCommander version in the system.

If you selected an existing ruleset, the prerequisites for that rule appear.

For more information about this field, see Working with the Versions tab.