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

Disabled state of flow nodes is persisted in cached diagrams

XMLWordPrintable

    • Icon: Bug Report Bug Report
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 2.7.0
    • None
    • frontend
    • None

      Reproduce:

      • Goto the branch analysis
      • Select Process A
      • Goto the Outlier Analysis
      • Select Process A

      Expected:

      • The Outlier Analysis shows the complete diagram without showing anything as disabled

      Observed:

      • The diagram displayed has the disabled flow nodes and sequence flows from the Branch Analysis

      —

      Hint:
      We cache viewer instances for performance reasons. We need to make sure that the disabled state is reset before committing a viewer instance to the cache.

        This is the controller panel for Smart Panels app

            [OPT-2738] Disabled state of flow nodes is persisted in cached diagrams

            Sebastian Stamm added a comment -

            While investigating this bug, I found another bug in the caching mechanism that I fixed with https://github.com/camunda/camunda-optimize/commit/60cc56fe8fab5bdf70aad16a3a6fd12b062f1916

            Now you don't need to select another process before switching to the outlier analysis for this bug to occur. This made this bug a bit more likely to occur and easier to reproduce.

            Sebastian Stamm added a comment - While investigating this bug, I found another bug in the caching mechanism that I fixed with https://github.com/camunda/camunda-optimize/commit/60cc56fe8fab5bdf70aad16a3a6fd12b062f1916 Now you don't need to select another process before switching to the outlier analysis for this bug to occur. This made this bug a bit more likely to occur and easier to reproduce.

              Unassigned Unassigned
              sebastian.stamm Sebastian Stamm
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: