Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-5269 Allow multi-definition reports to be grouped by process
  3. OPT-5538

Make flow node frequency class/string naming consistent

XMLWordPrintable

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

      We currently use a mix of, or one of, "frequency" and "count" when describing constants and classes relating to frequency reports. This is kind of redundant and we should instead consistently use one or the other throughout the BE codebase.

        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: