Application rules
Completing the General tab

Field

Description

Optional. Identify another application rule. The user RuleSet list includes the RuleSet versions identified on the General tab of the other rule (appearing below those listed in the arrays of this rule).

When assembling the RuleSet list during logon, the system incorporates the RuleSet Versions on the Application RuleSets array on the General tab of the other application rule. The Override RuleSets,Component and Shared RuleSets, and Available Production RuleSets arrays of that rule are ignored.

Select the first key part of another application rule on which this application depends; the other application is known as the parent.

Select PegaRULES if your application depends only on standard RuleSets, those listed in the PegaRULES.05.05.01 application rule.

Select the second key part of another application rule on which this application depends.

• Select 05.05.01 if you selected PegaRULES in the Name field and your application depends only on standard Process Commander V5.5 product rules, and not rules in other applications. The RuleSets and versions corresponding V5.5 product rules are listed in the PegaRULES.5.5 application rule.
• Select 5.4 if in the unusual situation that you selected PegaRULES in the Name field, your application depends only on standard V5.4 rules and features, and you want to execute with full V5.4 compatibility without using V5.4 capabilities.

This option affects only the scope of rules presented in design-time tools, not the run-time operation of the application. It affects:

• which RuleSets are included in the Application Explorer display
• which RuleSets are included in the Application Preflight tool (Application > Preflight)
• which RuleSets are included in automatic generation of product documentation (with the Application > Document and Application > Inventory menu items).

When checked, the Application Explorer tool includes RuleSets from the application identified in the Name and Version field, as well as RuleSets from this application rule. Similarly the Preflight tool includes rules from the parent (built-on) application in its analysis.

When checked, generated documentation includes use cases of the application identified in the Name and Version field, as well as use cases of this application.

For example, check this box if the current application rule provides rules that extend and customize a framework application built originally by the Enterprise Application accelerator, and you want rules from both the current application rule and the framework application rule to appear in developer tools and documentation.

Field

Description

Complete a row of this array for each RuleSet version, or an initial portion of a RuleSet version.

Optional. List one or more RuleSet versions of type Standard, one that has the Type on the Category tab of the RuleSet form set to Standard. (All RuleSets created in V5.3 and earlier are of the Standard type.)

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.)

When assembling a requestor's RuleSet list at logon, the system ignores the contents of this array unless this application rule is directly referenced on the Access tab of an access group that is available to the requestor. Stated differently: when this application rule is included for a requestor indirectly, through the Built on application field of another application rule, the contents of this array are not used.

Field

Description

This array provides a list of candidate RuleSet versions for the Production RuleSets array on the Access tab of the Access Group form. The order of entries in this array is not significant.

(A warning appears if you save an Access group form that references this application rule, but includes a production RuleSet version not listed here.)

Optional. 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.