Uploaded image for project: 'Drools'
  1. Drools
  2. DROOLS-5125

[DMN Designer] Node data type is lost after drag and drop in data type editor

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • DMN Editor
    • 2020 Week 10-12 (from Mar 2)
    • 3
    • Hide
      1. Create a new DMN diagram
      2. Add two custom data types
      3. Add one node to the diagram
      4. Set the node output type ref to one of created custom types
      5. Reorder custom defined data types by drag and drop feature
      6. Return to ndoe definition, its type will be lost
        Currently: the type will be <Undefined>
        Expected: the type is one of the custom data types
      Show
      Create a new DMN diagram Add two custom data types Add one node to the diagram Set the node output type ref to one of created custom types Reorder custom defined data types by drag and drop feature Return to ndoe definition, its type will be lost Currently: the type will be <Undefined> Expected: the type is one of the custom data types
    • Release Notes
    • Workaround Exists
    • Hide

      Set the data type of the node after reordering custom data types

      Show
      Set the data type of the node after reordering custom data types
    • When DMN diagram nodes has reference to some custom DMN data type, and this custom data type is edited, the reference in the node diagram is lost and node refers to '<Undefined>' data type.
    • NEW
    • NEW

      In dmn diagram, each nodes has its data type. The issue affects all nodes, after reordering custom defined data types. After such reordering data types of diagram nodes are lost.

              dadossan Daniel José dos Santos (Inactive)
              dadossan Daniel José dos Santos (Inactive)
              Jozef Marko Jozef Marko (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: