Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-2955 Allow usage of Camunda Process Events for Event-Based Processes
  3. OPT-3270

Store the Event Process data sources as part of the publish state DTO

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: L3 - Default L3 - Default
    • 3.0.0-alpha2, 3.0.0
    • None
    • backend
    • None

      When we publish an event based process, we create an EventProcessPublishStateDto, which is used for a few purposes such as storing the mappings and publish progress and of the process. In addition, the EventProcessInstanceImportMediatorManager uses it to create a process instance mediator which manages the creation of process instances for that event process.

      Now that event based processes can have more than one data source, this data structure should be updated to store each of these sources, and the last ingested timestamp will need to be a property of each source with a view to there being a dedicated mediator for each data source. The mediator and publishing progress logic will need to be updated too, to reflect the changes here. For the scope of this ticket, we only care about moving the single data source, so changing the structure of what we store.

      ATs:

      • The EventProcessPublishStateDto  stores all of the data sources used for a given event based process definition.
      • The mediator continues to create an event based process mediator and process instances continue to be created for event based processes.
      • The publish progress is still recorded

        This is the controller panel for Smart Panels app

              Unassigned Unassigned
              joshua.windels Joshua Windels
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: