Spike: Listeners as External Tasks

XMLWordPrintable

    • Type: Task
    • Resolution: Fixed
    • Priority: L3 - Default
    • 7.15.0-alpha3, 7.15.0
    • Affects Version/s: None
    • Component/s: engine
    • None

      Goal:

      • Evaluate feasibility to implement execution and task listeners as external tasks
      • Identify critical implementation challenges

      Priority:

      1. Execution Listeners
      2. Task Listeners

      Execution Listeners

      • Need to define exact runtime behavior, e.g.
        • should the invocation of subsequent listeners wait until the external task is finished?)
      • Defines a new wait state
        • Execution state must be persisted entirely to resume it successfully after external task is completed
        • All operations on wait state must still work when process instance is waiting for external task to complete
          • Migration
          • Cancellation (via API, boundary event, modification, ...)
          • APIs for requesting process instance state (e.g. activity instance tree, statistics queries, ...)

        This is the controller panel for Smart Panels app

              Assignee:
              Unassigned
              Reporter:
              Thorben Lindhauer
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: