Human Interactions - jBPM6 Developer Guide - page 196

Task-oriented user interfaces
A good way to finish the understanding of APIs provided by the Human task component is
to understand what kind of generic UIs will relate to it. These task-oriented user interfaces
should be generic enough to work for any kind of User task, but descriptive enough to
show sufficient information to the users to determine the task they should be working with.
These screens will contain and handle Human tasks in two different ways usually:
• Through the task lists
• Through the task forms
Task lists
When a user needs to check pending tasks, they need a screen that displays these tasks and
have an initial interaction with them. The list should contain enough information to under-
stand the pending task, but the information should be generic enough to be available for
most of the tasks.
The Tasks List view provided by tools such as KIE Workbench allows the user to choose
which tasks in the list to start working on first. A Tasks List view is an entry point for
users to understand what needs to be done. Users should have enough information from the
list to understand the nature of the tasks at hand and be able to prioritize them in order to
know which one to do first.
Some of the common pieces of information displayed in the Tasks List view are as fol-
lows:
• Task Name : This is a short and descriptive name of the task.
• Priority : This can help us sort tasks depending on their urgency.
• Status : A task could be in many different statuses and available to a user. It could
be reserved to that user, ready for one of its groups, or in progress when it is
already started.
• Created On : This is the date when the task was created.
• Due On : This is the date and time for when the task is due.
• Description : This is some textual description of the task that can contain contextu-
al information to clarify its purpose.
• Last Update : This is the last date when it was modified.