Red Hat Summit Red Hat SummitSupportConsoleDéveloppeursCommencer un essaiContact

Ce contenu n'est pas disponible dans la langue sélectionnée.

Chapter 6. Known issues in Red Hat Decision Manager 7.9.0

This section lists known issues with Red Hat Decision Manager 7.9.

6.1. Business Central
Copier lien

Package list fails to populate default package for imported projects [RHPAM-3209]

Issue: When a project contains many packages, and you try to create a new asset, the list of packages take some time to populate.

Steps to reproduce:

  1. Import a project which contains many packages.
  2. Go to the project page.

  3. Click Add Asset.

    The Assets window appears.

  4. Add any asset in the project.

  5. In the pop-up window, check the Package drop-down list.

    You receive Nothing selected option for some time.

Expected result: Package list is populating default package for imported projects.

Actual result: Package list is not populating default package for imported projects.

Workaround:

  • Make sure you have identical paths in both src/java and src/resources. In your Git repository, insert .gitkeep files to retain the empty folder structure.
  • In the asset pop-up window, manually select the <default> option in the Package drop-down list..

Collection editor is not opening for DRL based test scenarios [RHDM-1464]

Issue: DRL based test scenario throws an unexpected error when you open a collection editor for a list of some datatypes.

Workaround: None.

You cannot add a deployment unit when you create a container for the first time [RHPAM-3254]

Issue: You cannot add a deployment unit when you create a container for the first time, and you receive an unexpected system error.

Steps to reproduce:

  1. In Business Central, go to Menu Deploy Execution Servers.
  2. Under Deployment Units, click Add Deployment Unit.
  3. Enter the GAV values manually.
  4. Select the Start Deployment Unit? check box to start the service.

  5. Click Finish.

    You receive an unexpected system error.

Workaround: None.

The deployment unit fields are missing when you add a new deployment unit [RHPAM-3213]

Issue: When you add a deployment unit, fields that are available under Add Deployment Unit are missing.

Steps to reproduce:

  1. In Business Central, go to Menu Deploy Execution Servers.

  2. Under Deployment Units, click Add Deployment Unit.

    Deployment unit fields are missing.

Workaround: Deployment unit fields appear only if you navigate to Process Configuration and come back.

6.2. DMN designer
Copier lien

Decision service is missing inputData element in model with multiple DRDs [RHDM-1483]

Issue: When you reuse a decision component by adding it into a decision service node in a model containing multiple decision requirement diagrams (DRDs), the inputData element is missing from the resulting decision service node.

Steps to reproduce:

  1. Define multiple decision requirement diagrams (DRDs).
  2. In a DRD, define some decisions with inputs.

  3. In another DRD, define decision service and reuse the decision components from the previous DRD.

    Do not duplicate the inputs.

  4. Build and deploy the decision service.

  5. Do any of the following tasks:

    • Evaluate the decision to see the error reported in the description.
    • Verify the DMN source and see that inputData element is missing from the decision service .

Workaround: Add an inputData element manually into the resulting decisionService element.

DMN editor does not detect the changes from the Decision Navigator view [RHDM-1482]

Issue: DMN editor does not detect changes in the file when a decision requirement diagram (DRD) is renamed or removed from the Decision Navigator view.

Steps to reproduce:

  1. Rename a DRD from the Decision Navigator view.

  2. Click Save.

    You receive You have no unsaved changes alert window.

  3. Close the DMN editor.

    You receive You have no unsaved changes alert window.

  4. Reopen the DMN editor.

    The name of the DRD is still the same.

Workaround: Make a different change to the file which then enforces save or discard action.

The constraint value is missing in a decision table [RHDM-1460]

Issue: The constraint value is missing while defining a decision table.

Steps to reproduce:

  1. Create a DMN file with decision.
  2. Define a decision table.
  3. Set the first column type as a number.
  4. Save the asset.
  5. Close the editor.
  6. Reopen the asset.
  7. Go to the decision table.
  8. Select the input with type as a number.
  9. Open the Properties panel.
  10. Set the constraint in the Constraint value field.
  11. Select the output column.
  12. Select the input column again.
  13. Verify that the constraint value is missing.

Workaround: None.

The undo and redo operations do not work properly when you delete a node in decision requirements graph (DRG) [RHDM-1459]

Issue: In a model containing multiple decision requirement diagrams (DRDs), the undo and redo operations do not work properly when you delete a node in the decision requirements graph (DRG).

Steps to reproduce:

  1. Move the node to a DRD.
  2. Navigate to DRG.
  3. Delete the node from the DRG.
  4. Undo the changes.

Expected result: You can perform the undo and redo operations in DRG.

Actual result: You receive an error. When you confirm, the DRG is broken.

Workaround: None.

The undo and redo operations are lost when you switch between the diagrams [RHDM-1458]

Issue: In a model containing multiple decision requirement diagrams (DRDs), the undo and redo operations are lost when you switch between the diagrams.

Steps to reproduce:

  1. Open a DMN file with two or more decision requirement diagrams (DRDs).
  2. Make some changes. For example, move a node in one diagram.
  3. Switch to another diagram.

  4. Click Undo or press Ctrl+Z.

    The undo and redo operations are lost and nothing changes.

Workaround: None.

In Business Central, the DMN editor is unable to save the changes in the Properties panel [RHDM-1456]

Issue: When you change the name property in the Properties panel, try to save the changes, and reopen the editor, the DMN editor is unable to save the changes.

Steps to reproduce:

  1. Create a DMN file.
  2. Change the name of the DMN file in the Properties panel.

  3. Click Save.

    You receive You have no unsaved changes alert window.

  4. Close the DMN editor.

  5. Reopen the asset and check the the Properties panel.

    The changes are not saved.

Workaround: None.

DMN editor is reporting unsaved changes in the DMN files when there are no changes [RHDM-1453]

Issue: When you open a DMN file in Business Central and try to close the file without any changes, the DMN editor reports unsaved changes in the DMN files.

Steps to reproduce:

  1. In Business Central, go to Menu Design Projects.
  2. Click Try samples.
  3. Open Traffic_Violation project.
  4. Open Traffic Violation DMN file.

  5. Close the editor.

    You receive an Unsaved changes error pop-up.

Workaround: None.

6.3. Decision engine
Copier lien

testDoubleNaN fails after jitting on TypeCoercionTest [RHDM-1470]

Issue: You receive an AssertionError error in org.drools.modelcompiler.TypeCoercionTest#testDoubleNaN when a constraint is jitted.

Steps to reproduce:

  1. Run the following command in org.drools.modelcompiler module: 

    mvn clean install -Dtest=org.drools.modelcompiler.TypeCoercionTest#testDoubleNaN* -Ddrools.jittingThreshold=0

Workaround: None.

6.4. High-availability Business Central on premise
Copier lien

You cannot create multiple processes at the same time [RHPAM-3202]

Issue: When you create multiple processes at the same time, you receive an error message and multiple processes are not created.

Steps to reproduce:

  1. Create multiple processes at the same time.

    You receive an Activity not found error.

Workaround: None.

When you create a project, base-kie-project is created instead of the real name of the project [RHPAM-3193]

Issue: When you create a project, a project with the name base-kie-project is created instead of the real name of the created project.

Steps to reproduce:

  1. Create multiple projects with multiple users in the same space.

    The base-kie-project project is created.

Workaround: Delete and recreate the project or rename the project name from Settings tab.

You cannot create multiple projects at the same time [RHPAM-3192]

Issue: When you create multiple projects at the same time, you receive an error message and multiple projects are not created.

Steps to reproduce:

  1. Create multiple projects at the same time.

    You receive an error.

Workaround: None.

Red Hat logoGithubredditYoutubeTwitter

Apprendre

Essayez, achetez et vendez

Communautés

À propos de la documentation Red Hat

Nous aidons les utilisateurs de Red Hat à innover et à atteindre leurs objectifs grâce à nos produits et services avec un contenu auquel ils peuvent faire confiance. Découvrez nos récentes mises à jour.

Rendre l’open source plus inclusif

Red Hat s'engage à remplacer le langage problématique dans notre code, notre documentation et nos propriétés Web. Pour plus de détails, consultez le Blog Red Hat.

À propos de Red Hat

Nous proposons des solutions renforcées qui facilitent le travail des entreprises sur plusieurs plates-formes et environnements, du centre de données central à la périphérie du réseau.

Theme

© 2026 Red HatRetour au début