Enterprise Application accelerator - Completing the Work Detail form
This presentation is part of the Application Profile and Enterprise Application Accelerator Self-Study Course.
Transcript
Actors
The actors automatically default based on information entered in the Application Profile and can be modified on this screen.
Roles
Actors may play one or more roles in an application. Common roles include Originator, Manager, and Interested. Roles ultimately translate into work parties within PRPC.
It is up to the System Architect to determine the roles, or work parties, associated with a given actor. In this demonstration, Employee, Manager, and VP have been entered, which are associated with their respective actors.
You also have the option to associate the work party to a Current Operator or indicate if there will be multiple employees or managers associated with a single Leave request.
Work Types
Work Types, Supporting Categories, and Use Cases are redisplayed from the Application Profile to provide an opportunity for revision.
Work Type names will become concrete work classes when the accelerator generates the new application.
Supporting Type names are not work types. Rather, they are supporting types with associated use cases and will be included as part of the final documentation. These can be thought of like a task list for those team members responsible for security, system administration, etc.
Work Type Details
The Work Type Details screen solicits information about each work type, including: Display Label, Prefix, Starting Flow Name, Object Type, and the ability to Store the work type Separately.
- Display Label – which becomes the short description of the work class
- Prefix – which defines what will precede each work object ID when a work object is created
- Starting Flow Name – which is the process flow that will begin execution as soon as the work object is created
- Object Type – this defines whether this work type will be a standard work object, a cover or a folder.
- Store Separately – Use this checkbox to indicate if work objects need to be stored in different database tables, ultimately indicating a different class group.
The Accelerator suggests the Display Label, Prefix, and Starting Flow Names.