In most cases, use the New Application wizard to create new application records, rather than this form.
In special situations, you can create an application record by selecting Application
from the Application Definition
category.
Note: For optimal performance on a production system, minimize the number of distinct RuleSet lists in use by requestors. Rules assembly occurs for each record used by each distinct RuleSet list on each node. Limiting the number of distinct application records in use can aid performance (and simplify administration).
An application record 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, numbers, the ampersand, underscore characters, and dashes. Choose a name that is unique in the entire Pega Platform system. Rule resolution does not apply to application records. Note: By default, this name is displayed in the Short Description field on the form. The description is displayed in many places throughout Pega Platform, including the current application name on the Designer Studio header and user portals, in the Switch Application menu list, in application filters on Application landing pages, and on the Application Overview landing page header. If necessary, update the default to a unique, meaningful description no longer than 64 characters. Include a version number if users have access to multiple versions of the application. |
Version |
Enter a number to identify the version of this application record. 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 record. |
Note: If you are creating an application for user portals, such as pyCaseManager7, choose a Name that is meaningful to users and distinguishes this application from others they might use. (The name is displayed in the application selector on the portal.)
Select a RuleSet to associate with this application for use by the archive import and export tools. See associated ruleset.
Rule resolution does not apply to application records.