-
Feature Request
-
Resolution: Done
-
L3 - Default
-
None
Define, implement and document a lifecycle for task listener events that users can rely on. In particular, the following constraints should hold for a task:
- create is always the first event
- There is no event after complete or delete
- There is an immediate assignment event after create, if the task has an assignee based on the BPMN XML
- There is an update event when at least one task property has been changed. Setting properties before the create event is not regarded as a change/update.
- Events are not fired in Task Listeners, with the exception of the complete event.
Note: it is still possible to fire events through Task Listeners if the TaskService is used.
The solution provided for this ticket was developed together with the solution for Update Task Listeners (
CAM-10254).For a mapping of Task Events and Task Listeners, you can see this comment: https://app.camunda.com/jira/secure/EditComment!default.jspa?id=43617&commentId=117137
For a description of the Task Lifecycle (and the related design decisions), you can see this comment: https://app.camunda.com/jira/secure/EditComment!default.jspa?id=43617&commentId=117920