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

Attempt to normalize date variable strings to Optimize compatible format

    XMLWordPrintable

    Details

    • Type: Bug Report
    • Status: Done
    • Priority: L3 - Default
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.2.0, 3.2.0-alpha2
    • Component/s: backend
    • Labels:
      None
    • Epic Link:
    • Effort:
      Not defined

      Description

      When we import date variables, Optimize can only use the values for filtering if they match the Optimize date format specified as "yyyy-MM-dd'T'HH:mm:ss.SSSZ". It will accept and import other string formats for date variables, but any filtering for those variables will exclude results.

      We should either reject variable values that don't match the correct format or attempt to normalise these values on import before we store them to Elasticsearch.

      ATs:

      • Date variables that don't match the expected Optimize format are either rejected or normalised before storage
      • We allow missing/null values to be stored
      • We include the expected date variable format in our documentation and make this clearer for users

        mgm-controller-panel

        This is the controller panel for Smart Panels app

          Attachments

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              joshua.windels Joshua Windels
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Salesforce