Uploaded image for project: 'Red Hat Decision Manager'
  1. Red Hat Decision Manager
  2. RHDM-1153

Scenario Simulation shows misleading data type if DMN applies a constraint

    XMLWordPrintable

Details

    • 3
    • Release Notes
    • CR1
    • If DMN data type has a constraint over some field, then the data type of the field in not shown correctly to the user of Scenario and Simulation editor.
    • Hide
      1. Open an existing DMN file
      2. Add new structure, for example Vacation
      3. Add new field to Vacation, for example Price of type number
      4. Start edit Price field, click Add Constraints, fill some constraints for the Price
      5. Save all changes of the DMN file save and close it
      6. Create new Test Scenario for the previously used DMN
      7. Pick some column, expand the right site panel, pick Test Tools dock
      8. You will notice incorrect Price data type
      Show
      Open an existing DMN file Add new structure, for example Vacation Add new field to Vacation , for example Price of type number Start edit Price field, click Add Constraints , fill some constraints for the Price Save all changes of the DMN file save and close it Create new Test Scenario for the previously used DMN Pick some column, expand the right site panel, pick Test Tools dock You will notice incorrect Price data type
    • 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17)

    Description

      User has possibility to declare custom DMN data types. Furthermore such data types can apply a constraint to it. For example user can restrict a number to smaller range of values. The issue is a Scenario Simulation designer then shows a misleading data type in the UI.

      In the attached screenshots we have DMN Vacation data type, with a constraint over money field. Then in Scenario Simulation the data type if this field is money instead of number.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. RHDM-1435 Scenario Simulation type error popup when constraint applied to DMN data type

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. DROOLS-5317 Scenario Simulation shows misleading data type if DMN applies a constraint

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              yamer@redhat.com Yeser Amer
              rh-ee-jomarko Jozef Marko
              Jan Stastny Jan Stastny
              Jan Stastny Jan Stastny
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: