Human Interactions - jBPM6 Developer Guide - page 187

Human task component APIs
For this particular case, we've extended the process definition with which we started work-
ing in the previous chapters. We added two new User tasks to test and bug fix the require-
ment, and we added a model class to it called requirement to handle all process variables,
data inputs, and outputs.
The following screenshot shows the process definition we will be using in this chapter:
With these modifications, we now have two different groups in charge of Human tasks,
namely, developers, and testers. This will enrich the process enough to give us a playroom
for the next configuration steps.
The task service
The Human task component in jBPM6 follows the guidance of the WS-HT standard spe-
cification to construct a service that is accessible by both people and the process engine.
This specification defines specific calls that must be made to switch the state of Human
tasks. The main API for the Human task service is defined in the
org.kie.api.task.TaskService interface, as shown in the following code:
public interface TaskService {
...
void claim(long taskId, String userId);
void start(long taskId, String userId);