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

keep definition dependent filters when changing definition/version

    XMLWordPrintable

Details

    Description

      What is the desired functionality that you are missing?

      As a User, it is confusing to me that certain filters are automatically being removed just because I change the process or version. Instead I would like if it is somehow visualized that these filters do not apply anymore, but I could still save it as is and remove if necessary or wanted by me as the user. More details should be specified by asia.malina

       

      Which problem are you going to solve with this functionality?

      Today, filters that depend on the selected definition data (e.g. variable, flownode) get removed automatically when a different version or definition is selected. This is problematic since the user has to recreate the filters in many scenarios - especially when the definition is the same as it was previously. Additionally, sometimes the data is not available yet in the new version. 

       

      Context:
      The filters are definition dependent like variable, flownode, etc, get removed once the definiton or version is changed because there is a possibility that the filter is incompatible anymore. This is inconvenient because sometimes they just want to swtich to an older version where the filter is still compatible.

      Same problem exists with certain groupings or distribute by (e.g. Variable). This should be solved as part of the ticket or moved to a follow-up ticket.

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                omran.abazeed Omran Abazeed
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Salesforce