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

Accept all lowercase type field values for variable filters

      Currently, evaluating or saving a report fails when the report has a variable filter for a variable with a lowercase type (e.g. "string"). Since we read the variable names and types from the xml for decision reports and dmn has lower case variable types, we currently need to have a hack that converts the type to uppercase.

      I think it makes more sense for the backend to accept both uppercase and lowercase types and we get rid of this hack in the frontend.

        This is the controller panel for Smart Panels app

            [OPT-1941] Accept all lowercase type field values for variable filters

            There is an open ticket at jackson to handle polymorphic deserialization case insensitive https://github.com/FasterXML/jackson-databind/issues/1983
            Till then we can workaround this by also adding all lowercase type names to the subTypes of VariableFilterDataDto.

            Sebastian Bathke added a comment - There is an open ticket at jackson to handle polymorphic deserialization case insensitive https://github.com/FasterXML/jackson-databind/issues/1983 Till then we can workaround this by also adding all lowercase type names to the subTypes of VariableFilterDataDto.

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

                Created:
                Updated:
                Resolved: