Application Overview landing page
Basic, Work Types , Actors, Attachments, Advanced gadgets

Field

Description

(no label)

This application name as it appears in the Description field on the application rule form header.

Description

Text description for this application. Also appears in the Full Text Description field in History tab of the application rule.

For list view and summary view rules, this field may contain Reference directives or <pega:reference> JSP tags. The Description text becomes a report title. See More about List View rules.

For class rules, this field may not be blank.

Business Objectives

Optional. Expected business outcomes and objectives for this application.

Details and History

Rule

Name key value for this application. Cannot be edited.

Version

Version key value for this application. Cannot be edited.

RuleSet

The associated RuleSet. This value causes this application rule to be included when the Export gadget exports the RuleSet. This value does not affect rule resolution of this rule. You specify a version of this RuleSet when you add an attachment (Attachments gadget) to the application.

Ordinarily, select a RuleSet that is among those listed in the Application RuleSets on the General tab of the application rule form.

Created

Date indicating when the rule was created and by whom. Read-only.

This text also appears on the History tab of the application rule.

Updated

Date indicating when the rule was last updated and by whom. Read-only.

This text also appears on the History tab of the application rule.

History Details

Click this link see the Save history of this rule in a new window.

Field

Description

Name

Tree hierarchy of Work types (icon), use cases(icon) , and supporting use case category names.

• Work types describe the processing of concrete work objects with a life cycle that starts with creation and ends with resolution. Work types are assigned to use cases.

If the users of this application are to enter new work from a composite portal, this information is required.

• A use case represents a small processing unit performed by one or more actors DCO 5.5 for a given work type within an application. This information is derived from an associated Application Use Case rule.

• Supporting use case categories are the names assigned to processing use cases that support the operation of the application and processing of work types but do not create work objects, do not have a status, and cannot be routed to actors.

This information is also displayed on the Details tab of the application rule.

Description

• Use cases — Freeform details that describe the steps involved in completing the use case, the applicable edits, and expected behavior. This information also appears in the Description field on the Description tab of the Application Use Case rule form.
• Supporting use cases — Description of the use category. Also appears in the description field on the application rule Details tab.
• Work types — Indicates this application's work class in which its work object properties, HTML forms, and flows are supported.

Column

Description

Name

You can identify actors with the Application Accelerator. They also appear on the application rule Details tab.

Type

The type of this actor.

Count

The estimated number of this type of actor typically using the application.

Whether the count represents a total number of accesses over a certain time period, or concurrent accesses

The time period over which the total number of accesses by this actor type is estimated to occur. Options are Minute, Hour, Day, Week, Month, and Year. Selection is not required for concurrent accesses.

Access Method

Field

Description

Attachments

Displays a list of attachment names. These are the ones you entered when you added the attachments. Select a name to view its content.

Edit

Click to add or delete attachments. The Add / Remove Attachments button appears. Click to open the Attachments dialog.

To add an attachment:

1. Select or enter a unique name in the Name field in the New Attachments section. Names cannot contain spaces or special characters. For reporting purposes, consider prefixing the name with a purpose like those shown in the Suggested Names group in the pull-down list. For example, NonFunctionalRequirements_Proj1122_GRP21
2. Click Browse to locate and select the file you want to attach. Click Add to upload the file. A RuleSet Version pop-up dialog appears (appears only once if adding more than one attachment).
3. Select a version of the application's associated RuleSet and click Apply. This dialog appears only once if you enter additional attachments. The name appears in the Name section on the form.
4. Click Apply in the Attachments dialog to add the attachment and exit the form. The name appears as a link on the gadget and returns to Edit status. Click Close if you choose not to add the attachment.

To delete an attachment, open the dialog, select it from the Edit section, and click the icon. Click Apply to remove it from the attachment list.

Field

Description

Application Rule

Name key value of this application. Cannot be edited.

Application Version

Version key value for this application. Cannot be edited.

Owner

The organization, division, and organization unit to which this application belongs.

To open the organization chart and review or modify the organizational owner, hover the cursor to the right of the field to display the opener icon () and click it. kowal: per PROJ-420, this continues to have pencil icon opener

If the label No Org Structure Defined appears in the field, do the following to define an organization:

1. Click Edit
2. Click Change
3. In the Set Node pop-up dialog, select a node in the desired organization and click OK
4. Click Save in the gadget.

Main Class

For a Pegasystems solution framework, this field can identify a container class for the work pool. The Application Accelerator uses this field to identify solution frameworks.

Override RuleSets

Most applications do not include override RuleSet versions.

When assembling the RuleSet list at sign-on, the system works from the top of this list down. RuleSet versions appear in the following order, in two layers.

• Override RuleSets if any form the top layer. During rule resolution, this layer is searched first.
• The operator's private RuleSet, containing rules the operator has checked out, comprises the top of the second layer. (This RuleSet is not shown on the Application rule form). You have a private RuleSet only if the Allow Rule Check Out? checkbox on the Advanced tab of your Operator ID data instance is selected.
• Application RuleSets form the next lower group in the second layer.
• Component and shared RuleSets, if any, form the next group of the second layer.
• Standard RuleSets provided by Pegasystems, that start with the five-character prefix "Pega-" (not the four-character prefix "Pega"), always appear at the bottom of the second layer.

PMF Integration

If enabled, makes the Project Management features visible for developers using this application. See About the Project Explorer and Project Management interface. Proj-833 5.4 and Pega Developer Network article About the Project Management Framework.

Operators using this application see the Project Explorer tab in the Manage Rules panel, and specialized New, Save As, Check Out, and Check In dialogs which include a Project Management section.

A Declare ProjectMgmt link appears when this option is enabled. Click it to open the Rule-Declare-Pages instance Declare_ProjectMgmt. You modify this rule to customize the Project Management features. You can, for example, modify the standard Data-Project-Task.GetTaskList load activity to change the default properties used to identify tasks assigned to rules, or override the activity entirely to link the development process of this application with Pegasystems' Project Management Framework or another external project management tracking system.

See About the Project Explorer and the project management interface.

Password Protection

If enabled, users who have access to this application cannot edit any fields on the landing page without the required password. The edit button in a gadget contains a lock ( Edit ). The application rule also is protected.

If protection is disabled, a warning icon appears in this field. As a best practice, protect the application in most development environments.

To enable:

1. Click Edit.
2. Select the Password Protection checkbox.
3. Enter a password in the Enter and Confirm fields.
4. Click Save.

To disable:

1. Click Edit .
2. Enter the password in the Password Required to Edit pop-up window.
3. Clear the Password Protection checkbox.
4. Enter the password in the Enter and Confirm fields.
5. Click Save. All the gadgets are unlocked and can be edited. Application rule password protection is disabled.

Field

Description

Edit

Click to update the content management settings for this application. You can enable an application that is not currently enabled as well as update the current information.