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

Previously mapped events count entries are kept in the count response

XMLWordPrintable

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

      Context:
      In Optimize 2.7 we decided to exclude already mapped event count entries from the result (except the ones for the current targetFlowNode). Based on feedback we got we wan't to include them though.

      AT:

      • the exclusion of already mapped event entries done by `EventCountService.removePreviouslyMappedNonTargetEventsFromCounts` is removed
      • however if suggestions are active, already mapped events that are not mapped to the current targetNode should have the suggested flag set to false

        This is the controller panel for Smart Panels app

              Unassigned Unassigned
              sebastian.bathke Sebastian Bathke
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: