Most processes depict real-life, practical business or scientific scenarios which need the interactions of a human at least once in its workflow design. Typically, these interactions are initiated by the process itself, and requests a user input to proceed. For example, consider a "bank loan request" process which often requires the final decision to be taken by a human.
...
If human task management capability is not included in your product by default, you can add it by installing the above feature using the instructions given in section, Feature Management. Follow the instructions below to add a human task.
1.
- Log on to the product's management console and select "Human Tasks-> Add" under the "Main" menu.
...
- The "New HumanTask Package" window opens. Provide the file and click "Upload.
...
...
- The "Deployed Task Configurations" window opens with the newly-added human task listed. For example,
- Package Name: The name of the package.
- Task Definition: The task definition
- Type: Whether this definition is a Task or a
...
- Notification
- Status: The package status.
...
- Click on a selected "Task Definition".
Excerpt | ||
---|---|---|
| ||
Information on defining and adding human tasks to WSO2 BPS which facilitates human task management according to WS-Human Task specification. |
Writing a human task artifact
...
Element | Description | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Contains declarations of elements from WS- HumanTask namespace, that is <htd:logicalPeopleGroups> , <htd:tasks> and <htd:notifications> . | |||||||||||||||
| Used to import appropriate wsdl files. You should correctly specify the name spaces. Example:
| |||||||||||||||
| Used to specify logical people groups used in an inline human task or a people activity. The name attribute contains the name of the logical people group. The name must be unique among the names of all logical people groups defined within the
The group of clerks responsible for the region specified.
| |||||||||||||||
| Specifies the human tasks used in the business process.
| |||||||||||||||
| Used to provide the definition of an inline human task. The name attribute specifies the name of the task. The name must be unique among the names of all tasks defined within the It also consists of the
| |||||||||||||||
| Specifies the port types and operations of the human task.
| |||||||||||||||
| Used to assign people to process-related generic human roles.
| |||||||||||||||
| Provides annotations for users.
Example for WS-HumanTask 1.1 - WS-HumanTask Task Definition
| |||||||||||||||
| From element used to assign people for roles which have been specified in the business process. Argument element will pass values used in the people query.
| |||||||||||||||
| Specifies the user interface for human tasks or how the user interacts with the human task.
| |||||||||||||||
| Used to provide the definition of an inline notification.The name attribute specifies the name of the notification. The name must be unique among the names of all notifications defined within the
|
...
Code Block | ||
---|---|---|
| ||
createTaskOutput = function() { var outputVal = getCheckedRadio(); //get approve or not from radio button if(outputVal == 'approve') {return'<sch:ClaimApprovalResponse xmlns:sch="http://www.example.com/claims/schema"><sch:approved>true</sch:approved></sch:ClaimApprova lResponse>'; } else if (outputVal == 'disapprove') {return'<sch:ClaimApprovalResponse xmlns:sch= "http://www.example.com/claims/schema"> <sch:approved>false</sch:approved> </sch:ClaimApprov alResponse>'; } }; |
Output JSP will be used by the regional clerk user to approve the claim.
...
Info |
---|
An additional .jsp called <TaskName>-Reminder-input.jsp exists to send reminders for task caller. |
...
Excerpt | ||
---|---|---|
| ||
Information on defining and adding human tasks to WSO2 BPS which facilitates human task management according to WS-Human Task specification. |