|
|
RuleSet VersionsUse 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.
Creating branch RuleSets: When creating a branch RuleSet, first select Branch RuleSet before making any other selections in this form. The form refreshes to display the required fields for a branch RuleSet. See the Create a branch RuleSet section in this help topic.
Create a new RuleSet and version (for non-branch RuleSets)
Use the top section of the form to enter the key parts of both rules.
- A RuleSet has one key part — name
- A RuleSet version has two key parts — name and version
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. Special cases To create a language specific RuleSets 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. To create a RuleSet to support only access from mobile devices, follow the base RuleSet name with the _mobile suffix. See Understanding Pega-Mobile. Rule resolution To avoid circularity, rule resolution does not apply to RuleSet rules. Restrictions
|
|
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.
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 |
|
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) |
|
|
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 |
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 First select Branch RuleSet. After the form refreshes, select the branch ID and base RuleSet. Then click Quick Create or Create.
When the branch RuleSet is saved, the application rule is automatically updated to show the association between the branch and the branch RuleSet. By default, the name of the branch RuleSet is of the format baseRuleSetname_Branch_branchID.
Field |
Description |
| Branch RuleSet |
Select to create a branch RuleSet. |
| Branch ID |
Displayed if Branch RuleSet is selected. Select a branch to associate this branch RuleSet with. |
| RuleSet to Branch |
Select the RuleSet from which the branch RuleSet is based (the RuleSet it is branched from). You can branch any RuleSet in your RuleSet list, or which is otherwise available to you, except for your personal RuleSet. |
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.
- In the new rule form, enter RuleSet name and complete the rest of the form.
- Optionally, select the Update my current Application to include the new version (Quick Create only) checkbox. (Does not apply to branch RuleSets.)
- 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.
You can use the New form to add a new version to an existing, non-branch RuleSet. (Branch RuleSets always have a single version: 01-01-01).
- Open the form and select a RuleSet from the pull-down list in the RuleSet Name field.
- Update the version and the other fields as described above.
- Click Create. The RuleSet form opens.
- 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.
