Links may not function; however, this content may be relevant to outdated versions of the product.
Application Profile wizard - Completing the Work Types form
This presentation is part of the Application Profile and Enterprise Application Accelerator Self-Study Course.
The Work Types screen collects information about the:
- Work Type Name
- Supporting Type Name, and
- Atomic Use Cases
Work Type Name
A work type defines the kind of item that will be processed in a PRPC application. A work type is represented as a work object to an end user.
Each work object:
- Is uniquely identified,
- Is assigned to different individuals or systems for processing
- Maintains a life-cycle status
- Becomes completed or resolved at some point in time
Some examples of common work types might be a Loan Application Request, an Insurance Quote Request, an Expense Report, or a Help Desk Ticket.
For the Time-off application, the Leave Request is the work type that has been identified to be processed. An Employee will create a Leave Request work object and enter information about their time requirements. The request will then be forwarded to a Cost Center Manager for approval or rejection. If the request is approved by the Cost Center Manager and the time requirement is for an extended period, a Human Resources Manager will then make a final decision to resolve the request.
Atomic Use Cases
After entering a Work Type name, click the Define Use Cases button to display the five application use cases identified for the Leave Request.
Atomic use cases are smaller than some traditional use cases defined in other systems. An atomic use case in PRPC specifies:
- A single actor
- A single method or event that triggers an interaction, and
- Ownership of the work object is not changed in the use case
After entering the use cases for this work type, click “Done with Leave Request” to return to the Work Type screen. You can then add additional Work Types and use cases. For this application, there is just one work type.
Supporting Type Name
Supporting Type Names are categories of use cases that assist in the operation of the application and the processing of work types. They do not become work objects but support the processing of work.
PRPC pre-fills five of these supporting types in the profile:
- Common – use cases include attaching a memo as a local action or withdrawing a work object.
- Security includes use cases for user authentication,
- Navigation, which in our case will enable managers to use the Get Next Work button through the portal to retrieve the next request that they need to approve or reject.
- Data management
- System Administration
You can enter additional Supporting Type Names if needed. Supporting use cases also become use case rules, which can be incorporated into requirements documentation later.