Back Forward Application form
Completing the Details tab

 About Application rules

Note In most cases, as a best practice use the Application Overview landing page, rather than this rule form, to update information on the Details tab. See Application Overview landing page.

Use the Details tab to review, add, and update application detail including business objectives, work types, supporting use cases, and actors. This information is initially entered in an Application Profile and created by the Application Accelerator. proj-831 5.4 5.5 GRP-203 TASK-777

NoteIf your application includes a composite portal that incorporates the standard @baseclass.NewWork section (that allows users to enter new work objects), the Work Types area is required, not optional. List all work types in all work pools (class groups) of the application. See How to create a composite portal.

Field

Description
Business Objectives

Optional. List 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 use cases that describe the processing of concrete work objects with a life cycle that starts with creation and ends with resolution.

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

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

Select the class of a work type.
Work ID Prefix

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

NoteIf the users enter work objects for this application from a composite portal, a prefix you enter here overrides any prefix specified in a model rule. Leave blank to user the prefix in a model rule.GRP-203
Categories of Supporting Use Cases

arrayOptional. Lists the names assigned to processing categories of use cases that support the operation of the application and processing of work types. Supporting use cases do not create work objects, 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. DCO 3.2 GRP-2705
(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. DCO 3.2 GRP-2705
Access Method

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

Up About Application rules