Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-5167 Zeebe Data can be imported into Optimize
  3. OPT-5216

Save import data to definitions

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: L3 - Default L3 - Default
    • 3.5.0-alpha2, 3.5.0
    • None
    • backend
    • None
    • Not defined

      Currently, Zeebe definitions are saved with a string "Zeebe" as their engine. This doesn't make much sense in the context of Optimize. We should look at changing the structure/name of that field to better represent what is a data source rather than just an engine. For Zeebe definitions, we could store the prefix and partition for example

      ATs:

      • Process definitions store the appropriate data source import information regardless of type (Zeebe or Camunda engine)
      • Current definitions are migrated to match the new structure

        This is the controller panel for Smart Panels app

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

                Created:
                Updated:
                Resolved: