Human Interactions - jBPM6 Developer Guide - page 188

void delegate(long taskId, String usrId, String
tgtUsrId);
void fail(long taskId, String usrId, Map faultData);
void skip(long taskId, String usrId);
void forward(long taskId, String usrId, String
tgtEntityId);
void complete(long taskId, String usrId, Map
outputData);
List<TaskSummary> getTasksAssignedAsPotentialOwner(
String userId, String language);
List<TaskSummary> getTasksOwned(
String userId, String language);
...
}
This is just a simplification with the most used methods of the TaskService interface.
The behavior they provide is guided by the graph of the Human tasks' life cycle that we
saw in the Human tasks' life cycle section. In order to use it, we must initialize an imple-
mentation of it.
In order to have our Human task component available inside our classpath, we need to add
the dependencies necessary to get the task service classes working. In a Maven-based pro-
ject, we can add those dependencies by adding the following three dependencies to your
own Maven-based project's pom.xml file, just like the project in the code section of this
topic, which is in the chapter-06/human-task-components-api folder:
<dependency>
<groupId>org.jbpm</groupId>
<artifactId>jbpm-kie-services</artifactId>
<version>6.1.0.Beta3</version>
</dependency>
<dependency>
<groupId>org.jbpm</groupId>
<artifactId>jbpm-human-task-core</artifactId>
<version>6.1.0.Beta3</version>
</dependency>
<dependency>
<groupId>org.jbpm</groupId>
<artifactId>jbpm-human-task-audit</artifactId>