You are here: Reference > Rule types > Applications > Definition tab of the Application form

Definition tab on the Application form

The Pega Platform uses the information on this tab during logon to assemble a ruleset list. Use this tab to specify:

Built-on applications
Components in the application
The rulesets and versions that make up the application
Development branches for the application

The order of the ruleset lists on this tab affects the assembly order of your ruleset list and the operation of the rule resolution algorithm. You can reorder rulesets listed on this page by clicking and dragging fields within a specific section.

Specify a distinct version number for each ruleset. You can access rules in only one major version of a ruleset.

For information about ruleset assembly order, see Ruleset list layers.

Built on applications

When you create an application with the New Application wizard, the Pega Platform populates the initial field in this section with the value specified in the Built on application field from step 1 of the new application creation process.

For applications that depend only on standard Pega Platform rulesets, select PegaRULES and its highest available version in your system.

You can enhance the application's user experience by using client-side rendered UI templates. To enable these templates in your application, copy the pyIsUITemplatized rule to one of your production rulesets and set its value to true.

Additional applications can be built on to this application. For more information, see PDN article Using multiple built-on applications.

Enabled components

This section displays all components that are enabled in the application. You can install, enable, and disable new components in this rule form section.

For more information, see Components.

Presentation

Field

Description

Skin

Required. Specify a skin for this application.

The list of available skins is based on your profile and might include skins that are not available in the current application. If you save an application with an unavailable skin, the default pyEndUser skin is used instead.

If you add a new ruleset to the application, save the application before specifying a skin included in the new ruleset.

Render in HTML 5

Select to enable the application to be rendered in HTML5 document type (standards mode) and to take advantage of the latest browser features. This setting is selected by default for all new applications.

The Document Type setting on the Advanced tab of the Harness overrides this setting.

Advanced

Expand the Advanced section to display the additional fields listed below.

Field	Description
Component and shared rulesets	Optional: List any component or shared ruleset versions for the application.
Production rulesets (Customization)	Optional: List any production rulesets for the application. Rulesets in this section can be listed in any order. The rulesets specified in this section are also used on an Access Group form's Layout tab. For more information, see Access Group form – Completing the Definition tab.
Place properties on thread page only (5-4 or later)	When selected (default setting), at run time the system looks at the Thread level (`pxThread` page) for the current values of certain system-maintained properties. See Standard properties in the pxThread page (Code-Pega-Thread class). When cleared, the properties are maintained on both the `pxRequestor` page and one `pxThread` page for backward compatibility. However, only the `pxRequestor` values are accurate. If an application is built on another application where this check box is not selected, you cannot select the check box on the original application.
Log off redirection	Indicate how the user is directed after logging off from the application: To a log-off screen To the application log-on screen

Development branches

This section displays defined development branches by branch name in a tree structure. Because branch rulesets only have one version (01-01-01), the version number is not displayed.

Field

Description

Add branch

Click to add a development branch to the current application.

When you click this button, the Add a Branch ID pop-up dialog opens. You can either create a new branch for your application or add a branch from the system. Do one of the following actions:

Create a new branch by entering a name of between 3 and 16 characters. This value also provides the Branch ID key value for branched rulesets. A branch name must start with a letter and contain only letters, numbers, or hyphens. A best practice for the name is to relate it to the planned development work for that branch; for example, BUGFIX-Bug-42.
Select the name of an existing branch from the drop-down list. If the branch references branch rulesets, a message indicates that they will be available in your application.

Click Submit to save the branch to the branch tree.

You must save the application rule after adding a branch so that it is displayed on the list of available Branch ID values when you create a ruleset for that branch.

Branch

Displays the names of branches that are defined for this application in a tree structure.

Application rulesets

The Pega Platform automatically inserts the initial application ruleset values in this section when you generate your application by using the New Application wizard.

Open topic with navigation