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

Auto-generate processes based on events

XMLWordPrintable

    • 25

      Context:
      Once we have all the events ingested and already provide suggestions for the modelling, we can have a basic algorithm in place that can automatically generate processes based on the order of occurrence (similar what we already had in our prototype). This should be available to users in the frontend based on the design concepts, as a suggested event based process. Based on all of the event sources, the generated model should be a combined model using events from both camunda and external sources.

      AT:

      • An overall combined model is generated based on the event sources provided

      Out of scope:

      OPT-3260 Health Check of Event Based Process

        This is the controller panel for Smart Panels app

          1.
          Design for auto generation Design Part Done Unassigned
          2.
          Mini-spike Camunda BPM Assert Sub-task Done Unassigned
          3.
          Add REST-API for process autogeneration Feature Part Done Unassigned
          4.
          Create complete models based on external events Feature Part Done Unassigned
          5.
          Sort External event traces (and sequence counts) using secondary field Feature Part Done Unassigned
          6.
          Flattened Camunda models based on configuration Feature Part Done Unassigned
          7.
          Join models from multiple event sources Feature Part Done Unassigned
          8.
          Add auto generation of models to the user guide Sub-task Done Unassigned
          9.
          Make event source scopes inclusive for event counts Feature Part Done Unassigned
          10.
          Add a seperate option to edit event scope Sub-task Done Unassigned
          11.
          Create process by auto generation Sub-task Done Unassigned
          12.
          Add Convergent gateways to autogenerated models for external events Sub-task Done Unassigned
          13.
          Determine appropriate gateway type based on existing traces Sub-task Done Unassigned
          14.
          Find "best-fit" start/end events for external events for autogeneration Sub-task Done Unassigned
          15.
          Investigate whether we can auto-fit overlapping autogenerated models Sub-task Done Unassigned
          16.
          Create factories for event sequence count reader and trace state reader Sub-task Done Unassigned
          17.
          Investigate whether we can group event source elements inside BPMN Group Sub-task Done Unassigned
          18.
          Don't return empty xml when we can't generate external event model Sub-task Done Unassigned
          19.
          Only consider completed external event traces in sample used for gateway selection Sub-task Done Unassigned
          20.
          Add correct support for embedded subprocesses Sub-task Done Unassigned
          21.
          Reset the external event trace and sequence count indices Sub-task Done Unassigned
          22.
          Fix issue with ID generation during process autogeneration Bug Part Done Unassigned
          23.
          Adds gateways after process instance/start end if next source has multiple start nodes Feature Part Done Unassigned
          24.
          Determine the correct order of Camunda event sources in process autogeneration Feature Part Done Unassigned
          25.
          Start/End mapped events can't be edited in count view Bug Part Done Unassigned
          26.
          Generated models are using the IDs for node names instead of labels Bug Part Done Unassigned
          27.
          Include external traces in determination of event source order Feature Part Done Unassigned
          28.
          All process instance start/end event nodes have the same names Bug Part Done Unassigned
          29.
          Prevent overlap of multiple start events where possible Sub-task Done Unassigned
          30.
          Add e2e tests and screenshot generation for process autogeneration Sub-task Done Unassigned
          31.
          Make event ingestion sample data using correlatable trace IDs Sub-task Done Unassigned
          32.
          Mark autogeneration as beta feature in documentation Sub-task Done Unassigned

              Unassigned Unassigned
              johannes.heinemann Johannes
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: