Assign staff to a human task

Human Task

Websphere Integration Developer v612

Contact us...  

 

1. Assign staff to a human task
   1. People assignment roles and criteria
   2. People assignment settings
   3. Assigning roles to your human task
   4. Human task editor
   5. Related links

Assign staff to a human task

You need a way to associate a human task with a specific person or any member of a group of people who is qualified and permitted to complete the task. You can also assign roles (for example, Potential Owner, Reader) to a human task so that specific access rights can be granted.

People assignment roles and criteria

Roles and criteria interact to identify staff members according to their access rights. More specifically, authorization roles determine what their members are allowed to do in the runtime environment, and people assignment criteria define who will be member of an authorization role.

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. Criteria act to further refine the list of members who can claim the work. Officially, a people assignment criteria is a database query that retrieves a list of members from the runtime engine

People assignment settings 

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 kind of human task that you are working with.

1. Administrators

   Administrators have the authority to perform upper level duties like suspend, terminate, restart, force-retry, and force-complete.

2. Potential creators

   Potential creators can create an instance of the human task, but cannot start it.

3. Potential starters

   Potential starters have 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 invocation task.

4. Potential owners

   Potential owners can claim, work on and complete tasks.

5. Editors

   Editors 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.

6. Readers

   Readers are 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.

Assigning roles to your human task

A role is a set of employees who share the same level of authority. When it comes to working on tasks, the role that the person belongs to defines their authorization.

Human task editor

To create and manipulate tasks that will be assigned to human staff members in the runtime environment, use the human task editor.

 

The human task editor is a graphical programming environment that you use to configure the interaction between a service and its associated human participants, or between two humans.

Related links

1. Human tasks (IBM Guided Tour)
2. Authorization and people assignment (wps612)
3. Using people interactions 

 

 

Identify the escalation and notification mechanisms available for

Human Task

Websphere Integration Developer v612

Contact us...

 

1. Identify the escalation and notification mechanisms available for human tasks
   1. Related links

Identify the escalation and notification mechanisms available for human tasks

An escalation is a notification that is sent out when an expected result from a task has not been achieved within a set period of time. For example, an escalation could be used to alert a manager when a staff member is unable to complete a task by the deadline.

Note: The duration value for a human task is separate from the escalation function. Although the duration value will indicate when a task is due, it will NOT trigger an escalation.

 

When you create an escalation for your human task, you will need to know the following ahead of time:

1. The state that the task is in when the escalation period begins (this is also known as the activation state).
2. The state that you want the task to be in when the escalation period ends (it is when the task is NOT in this expected state at the end of the period that the actual escalation is thrown).
3. The escalation period, or how long you want the system to wait for the expected state to be reached before notification occurs.
4. The manner in which the notification takes place.

If you are creating more than one escalation for an activation state, you have two options:

1. Chained escalation In a chained escalation, the escalations are executed sequentially, or one after the other. In such a case, the first escalation must fully complete before the next one is initiated.
2. Parallel escalation With a parallel escalation, the escalations are in two separate paths, and are executed at the same time (or in accordance with the escalate after setting as described below).

Related links

1. Escalations (wps612) 
2. Human tasks (IBM Guided Tour)

 

Implement client interactions for human tasks

Human Task

Websphere Integration Developer v612

Contact us...  

 

1. Implement client interactions for human tasks (including API, human task manager, business flow manager)
   1. Setting up a user interface for your human task
   2. Before you begin: Client types and prerequisites
   3. Human Task Manager
   4. Business Flow Manager settings
   5. Related links

Implement client interactions for human tasks (including API, human task manager, business flow manager)

Setting up a user interface for your human task

The human task editor provides various client types that you can use to customize a user interface through which users can interact with the tasks in the runtime environment.

A client delivers task-related information to a staff member in the form of an interactive application. You can generate various types of clients for your human tasks, and use the generated clients to customize a user interface through which users can interact with the tasks in the runtime environment. Or, you can use generated clients to quickly demonstrate a human workflow, for example as a proof of concept or prototype.

Using the client generator, you can generate clients for both stand-alone human tasks that exist independently of a business process, and inline human tasks that exist within a business process. You can create one client for all the human tasks in a module, or generate one client per task. You can also generate one client for all human tasks in multiple processes or modules.

You can generate and use multiple web-clients for each human task. You may wish to provide a choice of user interfaces or to provide clients with different functionality for different roles or simply to provide basic clients that can be re-used with a different look and feel. You can also use generated clients at the same time as the Business Process Choreographer explorer; the effect on the human task instance is the same even though the user interface is different.

Before you begin: Client types and prerequisites

These are the types of clients that you can configure or generate for your human tasks. This topic contains useful information that you may need before you proceed to generate your client.

Human Task Manager

A human task manager provides services to run human tasks within an application server.

Business Flow Manager settings

A Business Flow Manager provides services to run business processes within an application server.

Related links

• Human tasks
• Using people interactions
• Human tasks (IBM Guided Tour)

Design human tasks

Human Task
Websphere Integration Developer v612
Contact us...

 

1. Design human tasks
   1. Scenario: Human workflow management
   2. Human workflow management considerations
   3. Inline and stand-alone human tasks
   4. Life cycle of a human task
   5. Related links

Design human tasks

A human task is, quite simply, a unit of work that involves a human. Quite often, this task requires that the human interact with other services, and thus becomes a task within a larger business goal.

Scenario: Human workflow management

Most business processes involve people in some way. This scenario provides a very high-level view of the concepts and steps for a process in which people play a significant or dominant role. See the documentation under Developing integration applications > Using people interactionsfor detailed information about the topics introduced here.

A process is composed of tasks. A human task is, quite simply, a unit of work that involves human intervention.

Human workflow management considerations

When you are planning a project that includes people in the process, there are some concepts that you need to understand in order to make sensible decisions.

Inline and stand-alone human tasks

There are two ways to implement a human task. Here is a discussion on when each type should be used.

Life cycle of a human task

A human task goes through a number of stages from its start to its finish.

Related links

1. Human tasks (IBM Guided Tour)
2. Using people interactions
3. Creating human tasks
4. About human tasks (wps612)