Optimize wrongly imports non JSON object variables

XMLWordPrintable

    • Type: Bug Report
    • Resolution: Fixed
    • Priority: L3 - Default
    • 3.8.0-alpha1, 3.8.0
    • Affects Version/s: None
    • Component/s: backend
    • None
    • Not defined

      Context:

      When adding support for native JSON variables we altered the ObjectVariableService in a way that some object variables that do not have the appropriate JSON serialisation are still imported due to an incorrect if/else condition. This needs adjusted to exclude this type of variable from being imported.

      This should also resolve the issue with UpgradeEsSchemaIT failing with an incorrect variable count.

      AT:

      • Optimize does not import non JSON serialized object variables
      • This is asserted in IT
      • UpgradeEsSchemaIT variable count assertion is reverted to equals rather than gte

       

      For QA: This can be tested by checking that Optimize does not import any object variables that do not have the json serialisation type. The default engine processes come with a variable called "approverGroups" that is an example of this, or alternatively this can be tested with external variable ingestion.

            Assignee:
            Unassigned
            Reporter:
            Helene Waechtler
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: