Back Forward Application form
Completing the Details tab
  1. About 
  2. New 
  3. General 
  4. Details 
  5. Specifications 
  6. Requirements 
  1. Associations 
  2. Advanced 
  3. Attachments 
  4. History 
  5. More... 

Note In most cases, as a best practice use the Profile Explorer, rather than this rule form, to update information on the Details tab. See Understanding the Profile Explorer.

The information specified on this tab controls what is available when you use the Application Document wizard to document the application and when you build on this application using the Application Profiler or Application Accelerator. You can use the fields and controls on this tab to review, add, and update application detail including business objectives, work types, supporting types, and actors. Typically, this information is initially specified in the application profile (using the Application Profiler) for this application, and set in the application rule when the application is created by the Application Accelerator or when entered in using the Profile Explorer.

You can use the Discover Work Types button to locate work types that are in the system and available to this application and add them to this tab. Adding such work types enables DCO capabilities for existing applications that were not initially developed using DCO. This button is displayed if there are work types available in the system to choose for this application that are not already listed in the Work Types array on this tab.

Caution Be cautious when removing work types already listed on this tab. If you remove a work type from the Work Types array and save the application rule, that work type will no longer appear in the New menu of the end user portals.

NoteIf your application includes a composite portal that incorporates the standard @baseclass.NewWork section (that allows users to enter new work items), the Work Types area is required, not optional. Typically, you list all work types in all work pools (class groups) of the application for which you want end users to be able to create work items using the New menu. See How to create a composite portal.

Field

Description
Application Classification  

Implementation Layer

If checked, indicates that this application is an implementation layer, which excludes this application from appearing among the list of applications presented in the Application Accelerator that are candidates for a "Built Upon" for the new application.

If this application was created by the Application Accelerator, the Implementation checkbox is checked for the implementation layer and not checked for the framework layer.

The value of this checkbox is descriptive; it does not restrict in any way the function or behavior of the application. You may check this box, even for a framework layer application, if you want to prevent the application from being selected as a Built Upon value.

Business Objectives

Optional. Lists the expected business outcomes and objectives for the application. Enter text to describe the outcome.

Work Types

arrayOptional. Lists the work types processed in the application. Work types are names assigned to sets of specifications that describe the processing of concrete work items with a life cycle that starts with creation and ends with resolution.

Case types added using the Case Designer appear on this array by default.

Note If you expect that the users of this application are to enter new work from a composite portal, list the work types for which those users are to create work items.

Show in New Work Menu

Select the checkbox in this column to display the corresponding case type's starter flows in the New menu on Case Worker and Case Manager portals.

The default checkbox selection depends upon the level of the corresponding case type:

  • Empty — Subcase flows do not appear.
  • Selected — Top-level flows do appear.

As a best practice, use the Actions > Show in / Remove from New Work menu in the Case Designer tree to control this setting. Your menu selection updates this checkbox. See Process and Rules category — Case Management page.

Caution If you remove a case type from the Work Types array and save the application rule, starter flows do not appear in the New menu. You can use the Case Designer tree's Show in New Work menu option to add the case type back to the array and restore the setting.

Name

Enter a name of the work type, for documentation purposes.

Implementation Class

Select the class of a work type.

Note The implementation class must be unique to the work type (a one-to-one relationship). You cannot specify the same implementation class for more than one work type.

Work ID Prefix

Enter the work item prefix (not including a final hyphen character).

NoteIf the users enter work items for this application from a composite portal, a prefix you enter here overrides any prefix specified in a data transform. Leave blank to use the prefix set in a data transform.

Icon

Identify an image that will appear, at runtime, on the tab of a work harness configured with a WorkArea control. Click the magnifying glass icon () to open the Image Viewer and select the binary file you wish to use.

In case management applications, use the Appearance setting of the Case Designer's Details tab to apply icons to case-type work harness tabs.

Discover Work Types

Displays if there are work types available in the system to choose for this application that are not already listed in the Work Types array. Click to add those available work types to this Work Types section. The system populates the list using the available work types.
Categories of
Supporting Specifications

arrayOptional. Lists the names assigned to processing categories of specifications that support the operation of the application and processing of work types. Supporting specifications do not create work items, do not have a status, and cannot be routed to actors.
Name

Enter the name of a supporting category.
Description

Enter a description of the supporting category.
Actors arrayOptional. Lists the names (actors) that are applied to a user, an external service, or a processing agent in the application.
Name

Enter the name of an actor.
Type

SmartPromptSelect the type of this actor.
Count

Enter the estimated number of this type of actor typically using the application.
(no label)

SmartPromptSelect whether the count represents a total number of accesses over a certain time period, or concurrent accesses.
(no label)

SmartPrompt Optional. Select 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

SmartPromptSelect the method this type of actor typically uses to access the application.

Up About Application rules