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

[DMN Editor] [BC Only] Saving dmn model is not working when using not() function

    XMLWordPrintable

Details

    • False
    • None
    • False
    • CR1
    • ?
    • Workaround Exists
    • Hide

      Customer is using the following as a workaround:

       
      As a workaround I rebuilt the decision table using a different hit policy (F) and replacing the not() statement with a hyphen and moving the first row of the decision behind the last row. In this case, it is a solution, though not elegant, but it won't do for all cases.

      Show
      Customer is using the following as a workaround:   As a workaround I rebuilt the decision table using a different hit policy (F) and replacing the not() statement with a hyphen and moving the first row of the decision behind the last row. In this case, it is a solution, though not elegant, but it won't do for all cases.
    • 2022 Week 44-46 (from Oct 31)

    Description

      The enclosed dmn file - Credit Risk (1).dmn cannot be saved. It can however be built and deployed, and is then working fine. 

      It seems that the problem is in the not() function which is in the BKM "Blocking Status Evaluation".

      When a change is made in the DMN model and pressed the Save button, a pop up message "Saving..." is shown. However, this message will not disappear and the only way to get out of this is to refresh the page but the change is not saved. See attached SavingDMN.png file. 

      Attachments

        1. Credit_Risk (1).dmn
          8 kB
        2. SavingDMN.png
          SavingDMN.png
          149 kB
        3. screenshot-1.png
          screenshot-1.png
          450 kB
        4. screenshot-2.png
          screenshot-2.png
          341 kB

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. DROOLS-6913 DMN DTAnalysis negation of non-compliant DMN missing enum

          • 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

          Task - Represents a small unit of work that is not end-user facing. DROOLS-6895 DMN Validation increased coverage for not(FEEL:string)

          • 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

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) DROOLS-4640 DMN Editor constraint on Type does not reflect in Decision Table

          • 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

              dadossan Daniel José dos Santos (Inactive)
              rhn-support-bkramer1 Biljana Kramer
              Barbora Siskova Barbora Siskova
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: