第8章 Known issues in Red Hat Decision Manager 7.8.1
This section lists known issues with Red Hat Decision Manager 7.8.1.
8.1. Business Central
A system error occurs when you add a deployment unit [RHPAM-3111]
Issue: When you add a deployment unit and manually enter incorrect GAV values, you receive an unexpected system error.
Steps to reproduce:
- In Business Central, go to Menu → Deploy → Execution Servers.
- Under Deployment Units, click Add Deployment Unit.
- Enter the non existent GAV values manually.
- Select the Start Deployment Unit? check box to start the service.
Click Finish.
You receive an unexpected system error.
Workaround: None.
The wait spinner is not present when you add a deployment unit, manually enter GAV values, and confirm the alert window [RHPAM-3114]
Issue: The wait spinner is not present after confirming the pop-up. You can modify the GAV values while the deployment is in progress.
Steps to reproduce:
- In Business Central, go to Menu → Deploy → Execution Servers.
- Under Deployment Units, click Add Deployment Unit.
- Enter the non existent GAV values manually.
- Select the Start Deployment Unit? check box to start the service.
- Click Finish.
In the Save Container Spec pop-up, click OK.
The alert window disappears and you can modify the GAV values while the deployment is in progress.
Expected result: The wait spinner is present after confirming the alert window.
Actual result: The wait spinner is not present after confirming the alert window.
Workaround: None.
When you apply constraint to a DMN data type, you receive an error in the scenario simulation [RHDM-1435]
Issue: When you apply a constraint to a DMN data type, you receive Wrong column mapping error pop-up in the scenario simulation.
Steps to reproduce:
- In Business Central, go to Menu → Design → Projects.
- Click Try samples.
- Open Traffic_Violation project.
- Open Traffic Violation DMN file and select Data Types tab.
-
To modify the
tViolationdata type, clicktViolation. -
To add the constraints to the
tViolationdata type, click the edit icon, click Add Constraints. -
Select Enumeration from the Select constraint type pull-down menu and add
50,90, and,130in the fields. -
Click OK, then click the check mark to the right of the
tViolationdata type to save your changes. - Click Save and close the DMN editor.
Open Violation Scenarios test scenario.
You receive Wrong column mapping error pop-up.
Workaround:
-
From the Test Scenario designer toolbar on the upper-right, click Export and export the
.CSVfile. - Click the affected property column header.
- Select the property from the Test Tools panel again.
- Confirm the pop-up to delete the values.
-
Import the originally exported
.CSVfile.
You cannot save a file when you try to rename the package from the source code [RHPAM-3119]
Issue: When you try to rename a package from the source code and close the editor before the reload is complete, you see an Unsaved changes error even when the data object is already saved in the new package.
Steps to reproduce:
- Open Business Central.
- Open any project.
- Create a data object.
- In the Source tab of a data object, change the package name.
- Click Save.
In the Information alert window, click + Yes, Move and confirm the changes.
You see Item successfully renamed notification.
Close the editor.
You receive Unsaved changes error.
Workaround: None.