Compose your own human task using a combination of the following building blocks
Roles and verbs interact to identify staff members according to their access rights. More specifically, roles define the permissions, and verbs define the members.
To understand how this works, you have to keep in mind that a task is assigned first and foremost to a role, not an individual. Each staff member in this role group has the permissions assigned to the role as a whole. Verbs act to further refine the list of members who can claim the work. Officially, a verb is a database query that retrieves a list of members from the runtime engine.
Use the staff settings to determine which roles can interact with your human task.
There are six possible roles to choose from, and those that appear will depend on the type of human task that you are working with.
An administrator has the authority to perform upper level duties like suspend, terminate, restart, force-retry, and force-complete. This actions can be executed by the Business Process Explorer..
A potential instance creator can create an instance of the human task, but cannot start it.
A potential starter has the authority to initiate an existing instance. The starter role is subtly different from that of creator, and although a creator can create a new instance, only a starter can start it. In many usage scenarios, the same employee fulfils both roles.
This role is only associated with an originating task.
A potential owner can claim, work on and complete tasks.
An editor can work with the content of a task, but cannot claim or complete it. For example, an editor can receive the work item to review a document and add comments, but an editor is not able to finish the task.
A reader is allowed to view tasks, but cannot work on them. This role can be used in situations where an employee wants to monitor as task without taking any action in it.
Use the client settings to determine how the staff members will interact with the tasks.
There are two default settings:
Select the Business Process Choreographer explorer to use the standard client that is delivered with this product.
With this option, the task is delivered to the staff member via an HTML-based web page. The look and feel of this web page is determined by the JSP values in the Client Settings table. You can modify these values as needed.
Select the portal client to specify a client that interacts with the WebspherePortalServer.
Use the escalation settings to specify how long to wait for a task to complete, and which role to notify when it doesn't.
There are three possible settings:
When a task is in the ready state, it is waiting to be claimed.
Configure the escalation settings to notify an authorized staff member should nobody claim it within the specified period of time.
When a task is in the claimed state, a staff member has accepted the work and should currently be working on it.
Configure the escalation settings to notify an authorized employee should the staff member fail to complete the work within the specified period of time.
When a task is in the subtask state, additional work was delegated to other staff members in order to complete the parent task.
Configure the escalation settings to notify an authorized employee should the staff member fail to complete the subtask within the specified period of time. The goal is to have this subtask completed before the parent task is escalated.