Throughout this guideline, the following terminology is used:
Process - an operation that consists of a single or multiple tasks. For instance, a typical process may be to create a
purchase order.
Task - a function that consists of a single or multiple discrete steps. For instance, in creating a purchase order, a
typical task would be to select an item to purchase. In a process with multiple tasks, the tasks can be linear (i.e. required
to be performed in a specific order) or nonlinear (i.e., can skip from task to task).
Step - a single action item within a task. For instance, in creating a purchase order, in selecting an item to
purchase, if the item has some options, the user may need to go through a single or series of steps to specify the desired
option(s). If a task has multiple steps, the steps can be linear (i.e., required to be performed in a specific order) or
nonlinear (i.e., can skip from step to step).
Object List Template - This template can be an initiation point for the checklist. Typically, the checklist can be launched by an action/navigation button or a functional icon within the table. In some self-service applications, the Home Page Template may also be used as the initiation point of the checklist. | |
Checklist Template - This template lists all the tasks included in the large process. The template consists of the following components:
|
|
Object Templates - Each task
within the checklist is an individual step in the overall process. A "Save for Later" button must be present on all Object Templates. This button saves changes to the database and returns the user to the checklist. The "Status" column of the checklist will be updated with the current status per task. With this approach, when users return to their work at a later time, it would be easy for them to determine where they left off to resume work.
|
|
Warning (or Messaging) Template - A warning page must be used to alert users
in the following scenarios of a checklist:
|
Image |
Description |
Indicates that no action has been taken on the task/step. | |
Indicates that the task/step is being worked on or in progress. |
|
Indicates that the task/step is completed. It has all the required information. | |
Indicates that the task/step contains an error. | |
Indicates that the task/step is not applicable. The "Not Applicable" icon can be used when 1) the user does not have security/privileges to the task, or 2) the setting of a previous controlling task on the checklist makes dependent tasks no longer required. |
Status Interaction Within a Multiple Discrete Steps Checklist (Linear)
Image |
Icon Name |
Size |
Possible States |
Description |
Not Started Indicator; |
16x16 | Status ONLY | Indicates that no action is taken on the task/step. | |
In Progress Indicator; inprogressind_status.gif |
16x16 | Status ONLY |
Indicates that the task/step is being worked on. |
|
Completed Indicator; completedind_status.gif |
16x16 | Status ONLY | Indicates that the task/step is completed. It has all the required information. | |
Error Indicator; erroricon_status.gif |
16x16 | Status ONLY | Indicates that the task/step contains an error. | |
Not Applicable Indicator; notapplicableind_status.gif |
16x16 | Status ONLY | Indicates that the task/step is not applicable. The "Not Applicable" icon can be used when 1) the user does not have security/privileges to the task, or 2) the setting of a previous controlling task on the checklist makes dependent tasks no longer required. |