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

Scenario Simulation type error popup when constraint applied to DMN data type

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.11.0.GA
    • 7.8.1.GA
    • Decision Central
    • None
    • Release Notes
    • CR1
      1. Export csv
      2. Click the problematic property column header
      3. Re-select the property in Test Tools
      4. Accept deleting the value
      5. Import the csv orginially exported
    • Hide
      1. Try Samples -> Traffic_Violation
      2. Go to Traffic Violation DMN file
      3. Go to Data Types
      4. tViolation -> Speed Limit -> Edit -> Add Constraints -> enumeration -> 50, 90, 130
      5. Confirm changes, Save DMN file
      6. Close editor, open Test Scenario "Violation Scenarios"
      7. See the warning dialog "Wrong column mapping"
      Show
      Try Samples -> Traffic_Violation Go to Traffic Violation DMN file Go to Data Types tViolation -> Speed Limit -> Edit -> Add Constraints -> enumeration -> 50, 90, 130 Confirm changes, Save DMN file Close editor, open Test Scenario "Violation Scenarios" See the warning dialog "Wrong column mapping"
    • 2020 Week 37-39 (from Sep 7), 2020 Week 40-42 (from Sep 28), 2020 Week 43-45 (from Okt 19), 2021 Week 07-09 (from Feb 15), 2021 Week 10-12 (from Mar 8), 2021 Week 13-15 (from Mar 29), 2021 Week 16-18 (from Apr 19)

    Description

      Follows up on RHDM-1153.

      When user creates a Test Scenario for DMN model and then adds constraint to an existing DMN Data Type property, the Test Scenario presents and error during opening complaining about incompatible type.

      1. It mentions still the property field (e.g. Speed Limit) instead of the real implementing type (number with constraints).
      2. To fix the Test Scenario the column needs to be redefined by selecting the property again.

      Even if some error is expected in such a case (adding constraint to an existing type), the error should inform the user better. But since the base type matches, it should not force the user to remove the column and add again, it should fail only when evaluated and the values not aligned with the constraint - ie at least when re-selecting the Data Object property in Test Tools the dialog should allow to "Preserve the values" when the type base is still the same.

      Attachments

        Issue Links

          is related to

          Task - Represents a small unit of work that is not end-user facing. DROOLS-6075 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. RHDM-1153 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.
          • Closed

          Activity

            People

              yamer@redhat.com Yeser Amer
              jstastny@redhat.com Jan Stastny
              Jan Stastny Jan Stastny
              Jan Stastny Jan Stastny
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: