Back Forward RuleSet Version rules
Completing the New or Save As form

 About RuleSet rules

  Show all 

Use the RuleSet Version: New form to simultaneously create a new RuleSet and an associated RuleSet version. Both rules are organized in one RuleSet form.

Select RuleSet or RuleSet Version from the SysAdmin category and click New to open the form.

There are two Save As forms: RuleSet and RuleSet Version. See Using the Versions tab.

 Create a new RuleSet and version

Use the top section of the form to enter the key parts of both rules.

Field

Description

RuleSet Name

Enter a RuleSet Name value, starting with a letter and containing only letters, digits, and dashes. 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, digits, and dashes. 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.

To create a language-specific RuleSet name, enter the base RuleSet name followed by a single underscore and then 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

  • CautionDon'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. NOT 128reworded B-16660 SR-1221B-24061 SR-7268 not 32

Version

After you enter a 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.

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.

Description

When you enter a RuleSet name, the system enters a unique two-part short description comprising the name and the default version. For example, if you enter 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.

Requires RuleSet and Version

This 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. For more information about this field, see Working with the Versions tab

Update my current Application to include the new version (Quick Create only)

When you enter a RuleSet name this checkbox appears. Select it if you want to add this RuleSet version to the top of the Application RuleSet list in the current application rule. If you select this box, you must use Quick Create to save the rule.

The system will not update the application rule if password protection is enabled. To disabled it, clear the Prevent others from changing this definition checkbox on the Advanced tab on the application form.

Create

Click to create the new RuleSet and version rules. When the RuleSet form opens, save the RuleSet. This also saves the RuleSet version. Do not save the version first by clicking the icon in the RuleSet version row on the Versions tab.

 Quick create

Use this method to create and save a RuleSet and a version in a single step. Unlike the normal create method, the RuleSet form does not appear and you do not have to save it.

  1. In the new rule form, enter RuleSet name and complete the rest of the form.
  2. Optionally, select the Update my current Application to include the new version (Quick Create only) checkbox.
  3. Click Quick Create . A confirmation dialog appears asking you whether you want to create the new RuleSet. Click OK. The system creates and saves the new RuleSet and version rules.

 Create a new RuleSet version

You can use the New form to add a new version to an existing RuleSet.

  1. Open the form and select a RuleSet from the pull-down list in the RuleSet Name field.
  2. Update the version and the other fields as described above.
  3. Click Create. The RuleSet form opens.
  4. Save the version by clicking the icon in the RuleSet version row on the Versions tab.

If you use Quick Create, the version is automatically saved; the form does not open.

landing page, division, organization unit, organizational RuleSet, ownership, RuleSet list
About Organization data instances
About Organization Unit data instances
About Division data instances
About Operator ID instances
About RuleSet versions

Up About RuleSet rules