Back Forward Application form
Completing the General tab

 About Application rules

  Show all 

Use the General tab to specify the RuleSets and versions that make up the application, and to identify another application rule that defines prerequisite RuleSets and versions. PROJ-1318

The system uses this information during log-on to assemble a RuleSet list for a user.

 Built on Application

Field

Description
Built on Application

SmartPromptOptional. 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.06.01.01 application rule.
Version

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

Select 06.01.01 if you selected PegaRULES in the Name field and your application depends only on standard Process Commander V6.1 rules, and not rules in other applications. The RuleSets and versions corresponding V6.1 product rules are listed in the PegaRULES.06.01.01 application rule.
Include Parent

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 > Tools > Preflight) byrnb 3/1/10
  • which RuleSets are included in automatic generation of product documentation (> Application > Tools > Document).byrnb 3/1/10

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. ZELEK 4/4/08 STEWS 4/7/08

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. GAJNJ 4/4/08

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

 About the RuleSets arrays

NoteThis tab contains three lists of RuleSet versions, for application RuleSets, component and shared RuleSets, and production RuleSets. The order of your entries within the three arrays affects the assembly of a user's RuleSet list and the operation of the rule resolution algorithm. (A rarely-used fourth list, for override RuleSets, appears on the Advanced tab.)

Enter RuleSets and versions in the same order as they are to appear on the completed RuleSet list, with the most specific appearing first.

When assembling the RuleSet list at sign-on, the system works from the top of each list down. RuleSets appear in the following order, in two layers.

In the Application RuleSets array, list zero or more RuleSets or RuleSets with a colon and version number. Follow the RuleSet Name with a colon followed by the version or initial portion of a version. Separate the RuleSet name from a version number with a colon, as in:

NoteList distinct RuleSets. A user or other requestor can access rules in only one major version of a RuleSet; access to version 04-10-15 includes access to 04-10-14 and 04-04-11, but not to 03-01-01. CLINIC Jan 2006

 Application RuleSets

Field

Description
Application RuleSets

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

 Component and Shared RuleSets

Field

Description
Component and Shared RuleSets

Advanced feature ArrayOptional. 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.) PROJ-1318REMOVED per ERNSG 5/13/09 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.

 Production RuleSets (Customization)

Field

Description
Production RuleSets

Array PROJ-1318 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.) GRIFK 2/15/08

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.

Up About Application rules