(WID/WPS) How does Human Task Manager work ?

Prerequisite for this post is basic understanding of human tasks.


When we model a human task, we can set a verb and a parameter that can be used to build a query to the user registry.Tasks are then created and assigned for all users in the result set of that query.


Below figure shows the link between modeling time and runtime. 
The attribute role of an activity is set to Potential Owner.
The verb is set to Group Members and the parameter to Approvers.
At runtime, this is used to build a SELECT ALL query. This query returns two users, John and Jane. John and Jane are members of the group Approvers and become potential owners of this new task.

Assigning tasks to users at runtime

Interaction between HTM & user registry

The Human Task Manager runs as a container within the application server.It is accessible through SCA or by way of specific APIs.These APIs or the client SCA interface can create a new task.When a new task is created, it follows following steps:

• HTM retrieves information from its database to build the query.
• HTM passes the query to the Staff Plug-in Provider using the Staff Service.
• The query is executed against the staff repository to retrieve a user or group of users.
• The query results are returned to the HTM.
• The new tasks that are created for the selected users are then stored in the database by the HTM.