Application form
Completing the Definition tab

Description

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 pyEndUser71 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.

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.

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

Description

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.

Note: 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.

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

To see the rules in a branch ruleset, expand the branch and click the branch ruleset's name.

• Lock - Select to lock all the branch rulesets associated with a branch. See Locking all rulesets within a branch.
• Merge - Select to merge the rules in the branch rulesets with the base ruleset by using the Merge Branches wizard. See Merging branches with the Merge Branches wizard.
• Package - Select to package all the branch rulesets within a branch into a JAR file. See Packaging a branch.
• Use for edit at runtime - Select to enable run-time editing when using the Live UI tool. Alternatively, use this menu to disable run-time editing from the selected branch.
• Delete from System - Select to delete the branch and its branch rulesets from the system. See Deleting a branch from the system.
• Remove from Application - Select to remove the branch and its rulesets from the application. See Removing a branch from an application.

After creating a branch, click to create a branch ruleset. See Creating branch rulesets.

Click to select which branches associated with this application to merge.

Description

Optional: List any component or shared ruleset versions for the application.

Optional: List any production rulesets for the application.

Note: 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.

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.

Note: 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.

Indicate how the user is directed after logging off from the application:

• To a log-off screen
• To the application log-on screen