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

[BC Included] DMN editor removing edges for duplicate Decision Nodes on canvas

    XMLWordPrintable

Details

    • 2021 Week 16-18 (from Apr 19), 2021 Week 19-21 (from May 10), 2021 Week 22-24 (from May 31), 2021 Week 25-27 (from Jun 21)
    • Hide

      Bottom-top approach:
      1. Create a Decision node A with a single Input linked.
      2. Drag the decision node A from Decision Components panel into canvas.
      3. Create another Decision node B that has the duplicated decision A as "from" relation. (A->B)
      4. Save
      5. Reopen
      6. The edge between original decision node A and Input is gone.

      Top-bottom approach:
      1. Create a Decision node A that is linked to another Decision node B (A->B).
      2. Drag the decision node A from Decision Components panel into canvas.
      3. Create an Input node and link it to the duplicated Decision node A.
      4. Save
      5. Reopen
      6. The link from Input is now made to the original Decision Node A while the duplicated has no links at all.

      Show
      Bottom-top approach: 1. Create a Decision node A with a single Input linked. 2. Drag the decision node A from Decision Components panel into canvas. 3. Create another Decision node B that has the duplicated decision A as "from" relation. (A->B) 4. Save 5. Reopen 6. The edge between original decision node A and Input is gone. Top-bottom approach: 1. Create a Decision node A that is linked to another Decision node B (A->B). 2. Drag the decision node A from Decision Components panel into canvas. 3. Create an Input node and link it to the duplicated Decision node A. 4. Save 5. Reopen 6. The link from Input is now made to the original Decision Node A while the duplicated has no links at all.
    • Workaround Exists
    • Hide

      Keep a single occurrence of Decision component per DRD (either don't duplicate or use multiple DRDs feature if needed).

      Show
      Keep a single occurrence of Decision component per DRD (either don't duplicate or use multiple DRDs feature if needed).

    Description

      There is an issue with edges handling in cases when a Decision component is duplicated in canvas.
      The common thing is that edges that were originally modeled are shifted or removed.
      There are two cases described in Steps to Reproduce, differentiated in the order of actions that took into the situation, but model-wise are supposed to be identical.

      Modeled diagram (and also expected outcome) :

      The resulting models upon reopen:
      Top-bottom case (the lower node is a duplicate):

      Bottom-up case (the above node is a duplicate):

      Attachments

        Issue Links

          Activity

            People

              dadossan Daniel José dos Santos
              jstastny@redhat.com Jan Stastny
              Jan Stastny Jan Stastny
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: