Creating a Process Project in the KIE Workbench - jBPM6 Developer Guide - page 152

User task

A comma separated list of group IDs or an expression of the form #{<expression>} that evaluates to a string object.
In the default Human task implementations of jBPM6, this property defines the actor's groups that can own this task.

Groups

This is the name of the user task. In the default Human task implementations of jBPM6, this property defines the task
name that should be displayed to the user.

Task Name

Comment

In the default Human task implementations of jBPM6, this property defines a comment for the task.

In the default Human task implementations of jBPM6, this property defines the priority of the task.

Priority

In the default Human task implementations of jBPM6, this property defines whether this task can be skipped or not.

Skippable

Notifications In the default Human task implementations of jBPM6, this property defines a set of time rules for sending specific e-mail
notifications to other users or groups when a task has not been started or completed within a specific amount of time.

In the default Human task implementations of jBPM6, this property defines a set of time rules for automatically reassign-
ing this task to another user or group when a task has not been started or completed within a specific amount of time.

Reassignment

The properties of the User task are tightly related to the default Human task implementa-
tion of jBPM6. This implementation is going to be introduced and explained in Chapter 6 ,
Human Interactions .

Manual tasks have the same attributes explained for an Abstract task. The variables you
can define in the DataInputSet and DataOutputSet properties depend on the
handlers you register for Send, Receive, User, and Manual tasks. We have discussed work
item handlers in Chapter 2 , BPM Systems' Structure . User tasks will have work item hand-
lers defined with the key Human Task , Manual tasks with the key Manual Task ,
Send tasks with the key Send Task , and Receive tasks with the key Receive
Task —all configurable from the runtime configuration of the different
WorkItemHandler implementations, which we have seen in Chapter 2 , BPM Systems'
Structure .

Going back to our process, we have six different tasks to define—one Business Rule task
(assign story points), one User task (develop requirement code), and four Abstract tasks
(notify developer of errors, notify developer of requirement changes, compile project to
Maven, and deploy compiled project). Let's now configure this process definition to
achieve the goal defined in Chapter 3 , Using BPMN 2.0 to Model Business Scenarios .