Use the Human Task to assign a job to an individual human based on work-party, any defined user-role or any custom conditions. It is represented as rectangular shape box as shown below:



Purpose

Human Task is used to support the allocation of a job to a human entity based on work party assignments, user-roles or any custom conditions. It has the mapping parameter screen to define the input and output parameters of the task. Human Task is needed when you need a user to intervene in a process.


Human Node Properties:

Human Task configuration panel has 4 different tabs to define properties.


  1. General

General Tab contains general information such as title name, task id, description etc.


All Settings in General Tab are shown below:


Property

Mandatory

Default

Description

Name

Y

Human

Default named as "Human". User can rename it according to work party or user roles. E.g.: Manager, Workparty Head etc.

ID

Y

System Generated

System Generated Unique Value.

Type

Y

humanTask

Shows the type of task.

Description

N

Desc

User can write here description of this task to state significance of Task.

Note:  User must click "Save Panel" to save all configuration changes.

  1. BusinessObject

To configure and map the Business Object for the input and output of any node, user must map the Activity Parameters inside Business Object tab. All mapped activity parameters are available for user to use inside Nodes. It is mandatory to set activity parameters in Business Object tab and map those parameters if user needs to use a value inside the activity.


Note: Activity Parameter mapping is not required if your process is not required to use a value within the activity or pass parameter values between nodes. For More details on Business Object, Process Parameters, Sub business objects and Data Parameter Mapping. Please refer section 6.4.3.4

  1. Assignment Policy

To set the type of assignment policy that is to be used for the human task allocation.



Settings inside Assignement policy Tab are shown below:

Property

Mandatory

Default

Description

Setting

Y

Lane

To choose the type of assignment method to be used. System provides 6 types as follows: Lane, Pull, Round Robin, Load Balance, Routing Policy and Custom.

More details for each Assignment policy method. Please refer Task Allocation & Queueing in section 6.4.3.3.1.1


Note:  User must click "Save Panel" to save all configuration changes.


  1. Load Entity:

Load entity settings are used to tag an existing Entity from ONEWEB Platform to your business process human node task. It also provides "Add Mapping Module" feature to add Module key and value for your mapping data. Delete/Trash icon on right side is used to remove any key value mapping.



All Settings in Load Entity Tab are shown below:

Property

Mandatory

Default

Description

Entity

Yes

-

The entity to be loaded from the To-do List when a user is assigned this task.

Key

No

-

The value on the entity to which data is passed.

Value

No

-

The value to be passed to that key.


Note: User must click "Save Panel" to save all configuration changes.