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.

        This is the controller panel for Smart Panels app

            [CAM-10724] Lifecycle for task listener events

            Thorben Lindhauer created issue -
            Thorben Lindhauer made changes -
            Summary Original: Lifecycle of task listener events New: Lifecycle for task listener events
            Thorben Lindhauer made changes -
            Description Original: Define, implement and document a lifecycle for task listener events that users can rely on. In particular, the following constraints should hold:

            * {{create}} is always the first event
            * There is no event after {{complete}} or {{delete}}
            New: 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}}
            Thorben Lindhauer made changes -
            Description Original: 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}}
            New: 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
            Thorben Lindhauer made changes -
            Component/s New: engine [ 11656 ]
            Thorben Lindhauer made changes -
            Link New: This issue is depended on by SUPPORT-6063 [ SUPPORT-6063 ]
            Thorben Lindhauer made changes -
            Fix Version/s New: 7.12.0 [ 15387 ]
            Thorben Lindhauer made changes -
            Remote Link New: This issue links to "Page (camunda confluence)" [ 13663 ]
            Nikola Koevski made changes -
            Assignee New: Nikola Koevski [ nikola.koevski ]
            Nikola Koevski made changes -
            Rank New: Ranked higher
            Nikola Koevski made changes -
            Status Original: Open [ 1 ] New: In Progress [ 3 ]

              Unassigned Unassigned
              thorben.lindhauer Thorben Lindhauer
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: