TrackTaskProcessor

Description

This ActionHandler is used to create variables for the each task that is finished.

After a task is finished, the following variables can be created:

Username of the actor
First name of the actor
Last name of the actor
Email of the actor
date/time when task was finished

With every loop, the variables can be created in two different ways:

With every repeat, a new variable is created (optionally can be activated): “nodename_taskname_firstname”. The activity name contains here also the loop count [e.g. (L:2)].
With every repeat, the old variable will be deleted (it will be always written): “nodename_taskname_firstname_lastLoop”. Only the activity name will be deleted with every repeat.

Class

com.dooris.bpm.actionhandler.TrackTaskProcessor

Parameter

Parameter name	Default value	Description	Valid examples

Parameter name	Description	Valid examples
`captureLoops`	For every repeat, a new variable is created, which contains the loop count if it is set to `true`.	`true`
`name`	Username of the actor will be stored if it is set to `true`.	`true`
`namefirst`	First name of the actor will be stored if it is set to `true`.	`true`
`namelast`	Last name of the actor will be stored if it is set to `true`.	`true`
`email`	Email of the actor will be stored if it is set to `true`.	`true`
`dateAndTime`	If “true”: Current date and time will be stored with the following format: dd.MM.yyyy HH:mm The Handler doesn't work retrospective, therefore the best is in the first activity of a process, the event type “Node-Enter” to use! dateAndTime knows of two parameters: _time _systemtime systemtime can be altered to the desired format which can be used for wordtemplates, emails, dashboard etc. eg dd.MM.yyyy or dd.MM.yyyy HH:mm:ss	`true` creates variable with name "taskNameStr + "_time" and value 17.03.2022 08:35 creates variable with name "taskNameStr + "_systemtime" and value 2022-03-17T08:35:00Z creates variable with name "taskNameStr + "_systemtime,dd.MM.yyyy" and value 2022-03-17

Example:

In this example, we have a part of a purchasing workflow and the TrackTaskProcessor is set under the Technical Issues node. In this case, starting from the preparation node, variables which contains name of the user will be created after each task is finished.

Parameter	Example Value

Parameter	Example Value
`name`	`true`