Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-3821 Make filtering more efficient and understandable (also break up Configuration Popover)
  3. OPT-4617

Migrate existing filters to use new API

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: L3 - Default L3 - Default
    • 3.3.0
    • None
    • backend
    • None
    • Not defined

      We need to make it clear at the API level what "type" of filter is being applied - whether its for the instance or the flow node. We also need to migrate all existing report filers to match the same data structure and be assigned the correct type.

      API will use level property, with possible instance or flownode values.

      For the migration, all current filters can be considered as instance filters apart from the following:

      - assignee/candidate filters are used on reports that grouped by User Task

      - assignee/candidate filters are used on reports that grouped by User Task Start/End Dates

      ATs:

      • API docs are updated
      • All filters have a level set
      • If a level is applied that is not allowed for that filter type, the filter is rejected

        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: