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

    • 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)

      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. 

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

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

                Created:
                Updated:
                Resolved: