Application rules
Completing the New or Save As form
|
|
In most cases, use the Application Accelerator to create new application rules, rather than this rule form. See About the Application Accelerator.
In special situations, you can create an application rule by selecting Application from the Application Definition category.
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) FITZI
webcast 9/21/06
An application rule has two key parts, a name and a version:
Field |
Description |
| 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 Designer Studio header, the Application Preflight report, and in Document wizard output. B-20057 pyProductName |
| Version |
Enter a name or number to identify the version of this application rule, in the format ZZ.ZZ.ZZ, where Z is a digit. As a best practice, use 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 gadgets. B-12838