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

Stale itemDefinition after update of Intermediate Message Catch Event

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • Kogito Tooling 0.8.0
    • BPMN Editor
    • False
    • False
    • Undefined
    • Hide
      1. Create a new process.
      2. Create process variables:
        • booleanProcessVar of type Boolean.
        • stringProcessVar of type String.
      3. Create intermediate Message catching event and set its Message property to any value, for example: "messageA".
      4. Create Data Assignment for this event with:
        Name: dataOut, Data Type: String, Target: stringProcVar
      5. Change the Type to Boolean and Target to booleanProcVar.
      6. Save the changes and see the the source code of the process.

      Actual result

      structureRef of itemDefinition with id="messageAType" is "String".

      Expected result

      structureRef of itemDefinition with id="messageAType" is "Boolean".

      Show
      Create a new process. Create process variables: booleanProcessVar of type Boolean. stringProcessVar of type String. Create intermediate Message catching event and set its Message property to any value, for example: "messageA". Create Data Assignment for this event with: Name: dataOut, Data Type: String , Target: stringProcVar Change the Type to Boolean and Target to booleanProcVar. Save the changes and see the the source code of the process. Actual result structureRef of itemDefinition with id="messageAType" is "String". Expected result structureRef of itemDefinition with id="messageAType" is "Boolean".
    • ---
    • ---
    • 2020 Week 49-51 (from Nov 30), 2020 Week 52-03 (from Dec 21), 2021 Week 04-06 (from Jan 25), 2021 Week 07-09 (from Feb 15)

      The value of structureRef of an itemDefinition created from an Intermediate Message Catch Event does not update in the XML after the Intermediate Message Catch Event has been modified and saved in the Kogito BPMN editor.

       

      Please see line:  line 5 of this BPMN.

       

      The "message" of the Intermediate Message Catch Event of the first draft of this BPMN was:  i-incident-event-created .  It originally mapped to a Boolean process variable called: booleanProcessVar .

      In the 2nd draft of this BPMN, I modified the Intermediate Message Catch Event such that the value of "message" is now:  i-responder-availability-verified.  The mapping was also changed to a String process variable called:  stringProcessVar.

       

      Notice that the value of the itemDefinition on line 5 of the XML remains Boolean (when it should be String).

       

      The downstream implications of this are extensive.  Kogito will auto-generate incorrect source code.  Errors occur once the kogito build tools attempts to compile the generated source code into byte-code.

        1. test-process.bpmn
          8 kB
        2. KOGITO-3932 - Expected Result.webm
          665 kB
        3. KOGITO-3932 - Actual Result.webm
          7.80 MB

              josephblt Wagner Lemos (Inactive)
              rhn-gps-jbride Jeffrey Bride
              Lubomir Terifaj Lubomir Terifaj
              Lubomir Terifaj Lubomir Terifaj
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: