Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-4544 Flow node status is added as a filter and removed from configuration popover
  3. OPT-4737

Existing flow node status configurations are migrated to be new filters

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 3.4.0-alpha1, 3.4.0
    • None
    • backend
    • None
    • Not defined

      Once the new filter type is supported, we need to migrate all existing flow node status selections in the config to be filters

      ATs:

      • The flow node status configuration options are now their equivalent view level filters
      • The flow node execution states have been removed from all documents in Elasticsearch
      • Flow node execution state enum and associated logic is removed from codebase
      • API docs for reports is updated

        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: