Uploaded image for project: 'Kogito'
  1. Kogito
  2. KOGITO-7331

Missing data when the serverless workflow definition is unmarshalled

XMLWordPrintable

    • False
    • None
    • False
    • Hide

      Workaround is to add the removed lines back manually

      Show
      Workaround is to add the removed lines back manually
    • ---
    • ---
    • 2022 Week 23-25 (from Jun 6), 2022 Week 26-28 (from Jun 27)

      Summary
      When you view a serverless workflow definition that contains non-required properties in our editor, some data is removed when the file is downloaded.
      For example:
      END

      {
         "name": "Next State",
         "type": "inject",
         "end": {
          "terminate": true,
          "continueAs": {},
          "compensate": false,
          "produceEvents": []
         }
      

      TRANSITION

      "transition": {
          "nextState": "Next State",
          "produceEvents": []
         }
      

      is changed to:
      END

      {
            "name": "Next State",
            "type": "inject",
            "usedForCompensation": false,
            "end": true
          }
      

      TRANSITION

      "transition": "Next State",
      

      but the expected outcome is:
      END

      {
         "name": "Next State",
         "type": "inject",
         "end": {
          "terminate": true,
          "continueAs": {},
          "compensate": false,
          "produceEvents": []
         }
      

      TRANSITION

      "transition": {
          "nextState": "Next State",
          "produceEvents": []
         }
      

      To see the issue inspect the before and after files.

      AC
      The marshalling/unmarshalling does not remove any data from users serverless workflow definition.

            jenrique@redhat.com Jaime Enriquez (Inactive)
            dhanak@redhat.com Dominik Hanak
            Dominik Hanak Dominik Hanak
            Dominik Hanak Dominik Hanak
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: