Configuration listener that must be attached to DeploymentService so it can react
to deployed units so it can register case event listeners per deployment unit.
Event listener that allows to fire notification based on mentions in the case comments
that refer to case roles - meaning all role assignments (users or groups) will be notified
whenever mentioned.
Defines human task specification to create new user task in ad hoc (dynamic) process instance
Expected parameters are:
NodeName - is a mandatory name of the task - accept variable expressions
TaskName - is a optional look up name of the task's form - accept variable expressions
ActorId - is an optional list of actors to be assigned - accept variable expressions
GroupId - is an optional list of groups to be assigned - accept variable expressions
Comment - is an optional comment/description of the task - accept variable expressions
Work item handler that allows to start new case instance based on following parameters:
DeploymentId - deployment id where that case definition belongs to (if not given deployment id of the work item will be used)
CaseDefinitionId - identifier of the case definition a new case instance should be started for
Data_NAME - case file data to be given when starting a case - NAME is the name of the case file input, can be given as many times as needed
UserRole_NAME - case role assignment as user entity where NAME is the name of the role that given user should be assigned to
GroupRole_NAME - case role assignment as group entity where NAME is the name of the role that given group should be assigned to
DataAccess_NAME - case file data access restriction where NAME is the name of the data that given roles should have access to, supports list of roles (comma separated)
Independent - indicates if the case instance is independent of the node that starts it - default is false
DestroyOnAbort - indicates if the case instance should be destroyed in case the work item is aborted, defaults to true
This work item allows to be executed in independent mode which means once the case instance is started it will complete work item without waiting for case instance completion.