Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-2955

Allow usage of Camunda Process Events for Event-Based Processes

XMLWordPrintable

    • 50

      Context:
      Often users have a hybrid of Kafka/legacy systems that produce events and parts of their application that are already automated by Camunda. To be able to have an end to end view on their system, we want to support to have event ingestion for Camunda out of the box.

      Given camunda events are available in a event log format that can be sequentially read during event based process instance generation (OPT-3195), Camunda event mapping support is needed in the event based process editor to make use of this data .

      AT:

      • camunda event sources can be managed per event based process
        • event based processes with camunda processes require each event user to have access to all of the associated processes in order to access the event based process
      • the REST API used to populate the event mapping table includes mappable camunda events for a particular camunda process
        • the current api is Event Counts
        • we need a way to specify camunda event filters (also applying the camundaProcess.eventScope to only show the desired subset of these events)
        • this only returns events, taskStart/End, processInstanceStart/End events, see OPT-3195
      • with a sequential camunda event source (OPT-3195) and camunda event mapping on event based processes in place, the event based process instance import uses the camunda event log to aggregate this data into event based process instances
        • data is correlated by the defined traceId location per camunda process => this id makes up the event based process instance id

      Designs:
      asia.malina

        This is the controller panel for Smart Panels app

          1.
          		 REST API to store Camunda Events Sources on event based processes Feature Part Done Unassigned
          2.
          		 Add Camunda processes as event sources to the event table Feature Part Done Unassigned
          3.
          		 Event Based Process is only accessible if the user is authorized to all event sources Sub-task Done Unassigned
          4.
          		 Reorder Mapping table column order Sub-task Done Unassigned
          5.
          		 Event source entries might have a null id Bug Part Done Unassigned
          6.
          		 Extend the API with typed event sources Sub-task Done Unassigned
          7.
          		 Adopt External Events Source handling to recent changes Sub-task Done Unassigned
          8.
          		 Event Mapping Table API for camunda Events Sub-task Done Unassigned
          9.
          		 Show Camunda Events of current sources in event mapping table Sub-task Done Unassigned
          10.
          		 Event Process Mapping Cleanup-API Sub-task Done Unassigned
          11.
          		 Call Event Mapping cleanup API on every relevant change Sub-task Done Unassigned
          12.
          		 Cleanup mapping on every event based process save Sub-task Done Unassigned
          13.
          		 Store the Event Process data sources as part of the publish state DTO Sub-task Done Unassigned
          14.
          		 Create mediators for each event source of an event based process Sub-task Done Unassigned
          15.
          		 Adjust event based process publish progress to consider the mediators for all its data sources Sub-task Done Unassigned
          16.
          		 Prevent storing of event process mappings with no event sources Sub-task Done Unassigned
          17.
          		 Handle possible race condition with fetching events where variables don't yet exist Sub-task Done Unassigned
          18.
          		 Camunda events have their variables written when being converted to process instance events Sub-task Done Unassigned
          19.
          		 'start and end' and 'start and end flownode events' are incorrectly switch Bug Part Done Unassigned
          20.
          		 Fix NPE when business key doesn't exist on Camunda Import source Bug Part Done Unassigned
          21.
          		 Missing traceId variable value causes import to get stuck Bug Part Done Unassigned
          22.
          		 Move camunda event correlation into the import service layer Bug Part Done Unassigned
          23.
          		 Extend definition API to allow to filter for camunda processes only Sub-task Done Unassigned
          24.
          		 Filter for non event processes in camunda events data sources Sub-task Done Unassigned
          25.
          		 Refactor event based process tests to include checks for multiple data sources Sub-task Done Unassigned
          26.
          		 update the whats new dialog Sub-task Done Unassigned

              Unassigned Unassigned
              felix.mueller Felix Mueller
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: