Application form
Completing the General tab

Field

Description

Specify another application rule, by its name and version, upon which this application is built. This other application is known as the "parent".

When assembling a user's RuleSet list during logon, the system incorporates the parent's application RuleSet Versions (specified in the Application RuleSets array in the parent's application rule form). In the user's RuleSet list, the parent's application RuleSets appear below the current application's RuleSets (specified in the Application RuleSets array on this General tab). The Component and Shared RuleSets, and Production RuleSets arrays of the parent's application rule are ignored.

Select PegaRULES and 06.03 for the name and version if your application depends only on standard PRPC V6.3 RuleSets (those listed in the PegaRULES.06.03 application rule). Select PegaDM and 06.03 to incorporate Decision Strategy Manager (DSM) in your application.

Select this checkbox if you want rules from both the current application and its underlying (built-on) application to appear in developer tools and documentation. The underlying application is specified by the Built on Application name and version fields, and is considered the "parent" of the application defined by this application rule.

For example, when this checkbox is selected, the Automated Unit Tests tab displays test cases that reside in the parent application's RuleSets, as well as RuleSets from the current application's application rule.

Note: Some areas in PRPC do not display rules in RuleSets that start with Pega-, regardless of whether the Include Parent checkbox is selected.

When selected, generated documentation includes specifications of the parent application (specified in the Built on Application fields by name and version), in addition to the specifications of the current application which builds upon the parent.

Some of the areas of the Designer Studio where rules from the parent are accessible (visible or selectable) when the Include Parent checkbox is selected are:

• Application Document wizard
• Guardrails landing page — Summary and All Warnings tabs
• Automated Unit Testing landing page

Field

Description

The initial entries in this array are typically added when the application is generated by the Application Accelerator or Application Express. To add a RuleSet:

1. Click to add a new row
2. Specify a RuleSet that has its Type set to Standard on the Category tab of its RuleSet form. (All RuleSets created in V5.3 and earlier are of the Standard type.)
3. After using the SmartPrompt () to select a RuleSet, complete the entry by entering a colon and RuleSet version or initial portion of a version after the RuleSet name. For example, an entry looks like OnboardingFW:01-01.

To create a new RuleSet for a new entry, click in its row. To remove an entry from this list, click next to the entry.

To move an entry to a new position in the list, click and drag it to the new location.

Field

Description

Click to add a development branch to the application.

When you click this button, a window opens in which to specify the name of the branch (also known as the branch ID). A branch name must start with a letter and contain only alphanumeric and dash characters. A best practice for the name is to relate it to the planned development work taking place in that branch; for example, BUGFIX-Bug-42. Click OK in the window to save the branch to the Branch tree.

To delete a branch, select the branch and click . The branch RuleSets associated with the branch remain in the system and must be explicitly deleted.

To move a branch to a new position in the tree, click and drag it to the new location.

On some occasions, you might have to save () the application rule after adding a branch to the Branches array, before creating branch RuleSets for that branch.

Displays the branches (by name) defined for this application in a tree-like structure. To see the branch RuleSets already associated with a branch, expand that branch in the tree.

To see the rules in a branch RuleSet:

1. Expand the branch that is associated with that branch RuleSet.
2. Click the branch RuleSet's name. The rule form for that RuleSet displays.
3. In the RuleSet rule form, click the number displayed in the All Rules column. A window opens that lists the rules that are in that branch RuleSet.

To associate a branch RuleSet with a branch, create the branch RuleSet using the Create Branch RuleSet button.

Click to merge the rules in the RuleSets in this branch to the base RuleSet. When you click this button, the Merge Branch RuleSets wizard starts.

Typically, you merge the branch's contents when development on rules in a branch is stable or complete. The merge action moves the branch's contents into those base RuleSets from which the branch's associated branch RuleSets were branched when the branch RuleSets were created.

Click to create a branch RuleSet. There must be at least one branch in the system to create a branch RuleSet. Typically you use the Add Branch button to first create the branch, and then the Create Branch RuleSet button to create the branch RuleSets for use in that branch.

When you click this button, the New form for creating a new RuleSet opens, with the Branch RuleSet checkbox selected. Complete creating the branch RuleSet using the New form. See RuleSets — Completing the New or Save As form.

On some occasions, you might have to save () the application rule after adding a branch RuleSet to a branch before creating rules in that branch RuleSet.

Field

Description

Optional. List any RuleSet versions of component or shared RuleSets here. (A component RuleSet has the Type on the Category tab of the RuleSet form set to Component. For a shared RuleSet, the Type is Shared.)

To add a RuleSet:

1. Click to add a new row
2. Specify a RuleSet of the appropriate type (that has its Type set to Component or Shared in its rule form).
3. After using the SmartPrompt () to select a RuleSet, complete the entry by entering a colon and RuleSet version or initial portion of a version after the RuleSet name. For example, an entry looks like OnboardingFW:01-01.

To create a new RuleSet for a new entry, click in its row. To remove an entry from this list, click next to the entry.

To move an entry to a new position in the list, click and drag it to the new location.

Field

Description

Optional. This array provides a list of RuleSets (names and versions) that are then referenced as candidates for selection in an Access Group form. If this application rule is to be used by developers or other operators who update rules, identify here one or more versions of production RuleSets. List at least some versions that are not locked. The order of entries in this array is not significant.

Specifying this list allows for making these RuleSets available to different access groups for people who use this application to store custom rules in these RuleSets. When RuleSets are specified in this array in the Application rule form, you can select them within the Access Group form for a particular access group. The Access Group form has a matching Production RuleSets array that corresponds to this one on the Application rule form.

After the RuleSets are specified here in the Application rule form, you can then open the Access Group form for an access group, and on the Access Group form's Layout tab, select one or more of these RuleSets in the corresponding Production RuleSets array for that access group. As a best practice, specify in the Application rule form's Production RuleSets array all of those RuleSets that you intend to specify in the access group form's Production RuleSets array. Otherwise, if you directly type RuleSets into the Access Group form's Production RuleSet array that do not also appear in the corresponding array on the Application rule form, a warning appears when you save the access group.

To add a RuleSet:

1. Click to add a new row
2. Specify a RuleSet that has its Type set to Standard on the Category tab of its RuleSet form. (All RuleSets created in V5.3 and earlier are of the Standard type.)
3. After using the SmartPrompt () to select a RuleSet, complete the entry by entering a colon and RuleSet version or an initial portion of a version after the RuleSet name. For example, an entry looks like MyReports:01-01.

To create a new RuleSet for a new entry, click in its row. To remove an entry from this list, click next to the entry.

To move an entry to a new position in the list, click and drag it to the new location.