Application form
|
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
If 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 |
Application Classification | |
Implementation |
If checked, indicates that this application is an implementation layer, which causes the application not to appear 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. Suprakash Das 9/29/10 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. List the expected business outcomes and objectives for the application. Enter text to describe the outcome. |
Work Types |
Optional. 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. If 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). If 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 |
Optional. 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 | Optional. 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 |
Select the type of this actor. |
Count |
Enter the estimated number of this type of actor typically using the application. |
(no label) |
Select whether the count represents a total number of accesses over a certain time period, or concurrent accesses. DCO 3.2 GRP-2705 |
(no label) |
Optional. Select the time period over which the total number of accesses by this actor type is estimated to occur. Options are |
Access Method |
Select the method this type of actor typically uses to access the application. |