Application
rules
Completing the New or Save As form
|
|
An application rule has two key parts, a Name and Version.
For best
performance on a production system, minimize the number of
distinct RuleSet lists in use by requestors. Rules assembly
occurs for each rule used by each distinct RuleSet list on each
node. Limiting the number of distinct application rules in use
can aid performance (and simplify administration)
Field |
Description |
| Type |
Select |
| Name |
Enter a name for this application rule. Start the name with a letter and use only letters, digits, ampersands, underscores, and dash characters. Choose a name that is unique in the entire Process Commander system. Rule resolution does not apply to application rules. This name identifies the application in the output of the Application Inventory tool, Application Preflight report, and Application Document tool. |
| Version |
Enter a name or number to identify the version of this application rule, in the format ZZ.ZZ.ZZ, where Z is an digit. As a best practice, use the format values that are meaningful to you. This key part has no specific meaning but together with the name uniquely identifies the application rule. |
Rule resolution does not apply to application rules. You can associate a RuleSet with the application rule, for use by the Archive import and export tools.