# Human Task
The **Human Task** is used to assign a task to a human participant during process execution.\
It enables human interaction within an otherwise automated workflow and is represented by a **rectangular BPMN task node**, as shown below.
Human Tasks are essential whenever a process requires **manual decision‑making, approval, review, or data input** by a user.
***
### Purpose
The **Human Task** supports the allocation of work to a **human entity**, based on:
* Work Party assignments
* User roles
* Custom assignment conditions
It allows users to intervene in the process flow and provides a **mapping parameter screen** to define the **input and output data** required for task execution.
***
### Human Task Configuration Overview
The Human Task configuration panel consists of **four main tabs**, each defining a different aspect of task behavior:
1. **General**
2. **Business Object**
3. **Assignment Policy**
4. **Load Entity**
Each tab is described below.
***
### General Tab
The **General** tab defines basic metadata for the Human Task, such as name and description.
#### General Properties
| Property | Mandatory | Default | Description |
| ----------- | --------- | ---------------- | --------------------------------------------------------------------------- |
| Name | Yes | Human | Default task name. Can be renamed (e.g. Manager Approval, Work Party Head). |
| ID | Yes | System‑generated | Unique identifier generated by the system. |
| Type | Yes | humanTask | Defines the task type. |
| Description | No | Desc | Description explaining the purpose of the task. |
> **Important**\
> Click **Save Panel** to persist any configuration changes.
***
### Business Object Tab
The **Business Object** tab is used to configure and map **input and output parameters** for the Human Task.
This mapping enables:
* Passing data into the task
* Collecting user input
* Sharing data between tasks
#### Key Points
* Activity parameters must be mapped if the task requires data
* Mapped parameters become available inside the task
* Mapping is **mandatory** only when data is needed for task execution
> **Note**\
> If the process does not require data exchange for this task, Business Object mapping can be skipped.
For detailed information about Business Objects, Process Parameters, and mapping, refer to the **Business Object Data Mapping** section.
***
### Assignment Policy Tab
The **Assignment Policy** tab defines how the Human Task is assigned to users.
#### Assignment Policy Settings
| Property | Mandatory | Default | Description |
| -------- | --------- | ------- | -------------------------------------------------------------------------------------------------------------------------- |
| Setting | Yes | Lane | Defines assignment strategy. Available options include: Lane, Pull, Round Robin, Load Balance, Routing Policy, and Custom. |
Each assignment strategy controls **how tasks are distributed** among users.
For detailed explanations of assignment methods, refer to the **Task Allocation & Queuing** section.
> Remember to click **Save Panel** after updating this tab.
***
### Load Entity Tab
The **Load Entity** tab connects the Human Task to a **UI Entity** from the ONEWEB platform.\
This defines which user interface will be displayed when the task appears in a user’s To‑Do list.
#### Load Entity Properties
| Property | Mandatory | Default | Description |
| -------- | --------- | ------- | ------------------------------------------- |
| Entity | Yes | — | UI entity loaded when the task is assigned. |
| Key | No | — | Entity attribute used for data mapping. |
| Value | No | — | Value passed to the entity attribute. |
Additional features:
* **Add Mapping Module** to define key‑value mappings
* **Delete (Trash) icon** to remove mappings
> Click **Save Panel** to store Load Entity configuration.
***
### Summary
The **Human Task** is the primary mechanism for introducing **human participation** into a ONEWEB process.
Key takeaways:
* Used for approvals, reviews, and manual decisions
* Supports role‑based and rule‑based assignment
* Allows full configuration of data input/output
* Integrates seamlessly with UI entities
* Critical for real‑world, user‑driven business workflows
Proper configuration of Human Tasks ensures smooth collaboration between **business users and automated systems** within a process.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.onewebstack.com/oneweb-platform-th/designer-reference/process-designer/process-designer-component/activity-nodes/human-task.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.