Chapter 5. Known issues

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

5.1. Business Central

When you add a deployment unit and manually enter GAV values, the runtime strategy is not set to the configured default value [RHPAM-2623]

Issue: In Business Central, you can configure a default runtime strategy. However, when you add a new deployment unit and enter the group, artifact, and version (GAV) values manually, the runtime strategy is not set to this configured default.

Steps to reproduce:

  1. Import the Evaluation_Process sample project into Business Central.
  2. In the project window, click Settings and then select DeploymentsGeneral Settings.
  3. Change Runtime Strategy to Per Process Instance.
  4. Click the drop-down list next to the Build button and select Build & Install.
  5. In the main menu, select DeployExecution Servers and then click Add Deployment Unit.
  6. Enter the values in the following list into the corresponding fields:

    • Name: evaluation:evaluation:1.0.0-SNAPSHOT
    • Group Name: evaluation
    • Artifact Id: evaluation
    • Version: 1.0.0-SNAPSHOT
  7. Click Next. If you click Finish at this stage, the result will not be changed.
  8. In the window that appears, note that the runtime strategy is Singleton.
  9. Click Finish.
  10. Start the deployment.
  11. When the deployment has completed, click the deployment link, for example http://localhost:8080/kie-server/services/rest/server/containers/evaluation:evaluation:1.0.0-SNAPSHOT.
  12. View the runtime strategy in the XML information displayed at the link, for example:

            <config-items>
                <itemName>RuntimeStrategy</itemName>
                <itemValue>SINGLETON</itemValue>
                <itemType>BPM</itemType>
            </config-items>

Expected result: The runtime strategy is Per Process Instance.

Actual result: The runtime strategy is Singleton.

Workaround: When you create a new deployment unit, select the artifact from the list without entering GAV values manually. Alternatively, manually select the runtime strategy when creating a new deployment unit.

You cannot start a task if the Elytron adapter is installed [RHPAM-2450]

Issue: If Business Central on Red Hat JBoss EAP is integrated with RH-SSO using the Elytron adapter, errors are displayed after a task is started.

Steps to reproduce:

  1. Install Red Hat Decision Manager on Red Hat JBoss EAP.
  2. Configure Business Central with RH-SSO using the Elytron adapter.
  3. Import a process sample.
  4. Start the process.
  5. Start a task.

Expected result: The task starts correctly.

Actual result: The task does not start and an error is displayed.

Workaround: Use the legacy adapter instead of the Elytron adapter. Enter the following command to install the legacy adapter:

./bin/jboss-cli.sh -c --file=bin/adapter-install.cli

In the guided rule editor, you cannot use the is contained in comma separated list constraint in combination with complex values [RHPAM-2457]

Issue: In the guided rule editor, you cannot use the is contained in comma separated list constraint in combination with complex values. Complex values are values that contain a comma or are wrapped by brackets.

Workaround: None.

The state of a Decision Server is not updated in the server template n Business Central after the server disconnects and reconnects to Business Central [RHPAM-2544]

Issue: After a Decision Server disconnects and reconnects to Business Central, the state of this server in the server template in Business Central is not updated. For example, if the Decision Server is switched from development mode into production mode, Business Central does not recognize the change.

Steps to reproduce:

  1. Ensure a Decision Server is connected to Business Central and set to development mode.
  2. Shut down the Decision Server.
  3. Reconfigure the Decision Server to use production mode. Do not change other configuration settings.
  4. Start the Decision Server.
  5. Deploy a service with a SNAPSHOT version onto the server template.

Expected result: Business Central displays a message that the server is in production mode and the service can not be deployed.

Actual result: The deployment starts and fails.

Workaround: Manually delete the server template in Business Central before restarting the server. Alternatively, change the name of the server when you reconfigure it.

In scenario simulation, the right-hand Test Tools panel displays the name of a field instead of the type [RHDM-1153]

Issue: In come cases, instead of the type of a field, the right-hand Test Tools panel displays the name of the field.

Steps to reproduce:

  1. Open an existing DMN file in Business Central.
  2. Add a new structure, for example, Vacation.
  3. Add a new field to Vacation, for example, Price of type number.
  4. Start editing the Price field.
  5. Click Add Constraints and enter some constraints for the Price field.
  6. Save all changes to the DMN file and close the file.
  7. Create a new test scenario for the DMN file.
  8. Select a column.
  9. Expand the right-hand panel.
  10. Click the Test Tools panel.

Expected result: The panel displays the name and type of the field: Price[number].

Actual result: The panel displays the name of the field twice: Price[Price].

Workaround: none.

5.2. High availability

In a high-availability authoring environment, when one user imports a project, another user is unable to see it [RHPAM-2470]

Issue: When multiple users connect to a high-availability Business Central and one user creates a project, another user cannot see the project.

Steps to reproduce:

  1. Log in to Business Central as two different users (A and B) from two different hosts or browsers.
  2. As user A and as user B, open the same space.
  3. As user A, import a project using an external Git repository URL.

Expected result: As user B, you can see the imported project in the space.

Actual result: As user B, you cannot see the imported project in the space.

Workaround: As user B, reload the space.

In a high-availability authoring environment, project creation fails when a Business Central node is down [RHPAM-2475]

Issue: When you create a project, the project creation does not complete. The cause is one Business Central node in a high-availability authoring environment going down.

Workaround: Create the project again.

In a high-availability authoring environment, asset creation is not completed when a Business Central node is down [RHPAM-2476]

Issue: When you create an asset, the asset is not indexed. It is displayed in Business Central but you cannot use it. The cause is one Business Central node in a high-availability authoring environment going down.

Workaround: In the Project Explorer view, open the asset and click Save.

5.3. DMN designer

When you import a data object from a Java class, fields that have the Java Date type are not converted to the DMN date type [RHDM-1145]

Issue: When you use DMN designer to import a data object from a Java class and the class has a field of type Date, the resulting DMN field does not have the DMN date type.

Steps to reproduce:

  1. Open a project in Business Central.
  2. Add a Java data object.
  3. Create a java.util.Date field in this object.
  4. Save and close the Java class.
  5. Open a DMN file.
  6. Select the Data Types tab.
  7. Click Import Data Object.
  8. Select the Java class that you created.
  9. Click Import.
  10. Check the type of the field into which the java.util.Date field was converted.

Expected result: The field has the type date or date and time.

Actual result: The field has the type Any.

Workaround: Manually change the type of the field to date or date and time.

When you import a data object from a Java class, a field of the Java List type is not converted to the DMN collection type [RHDM-1144]

Issue: When you use DMN designer to import a data object from a Java class and the class has a field of type List, the resulting DMN field does not have the DMN collection type.

Steps to reproduce:

  1. Open a project in Business Central.
  2. Add a Java data object.
  3. Create a List field in this object.
  4. Save and close the Java class.
  5. Open a DMN file.
  6. Select the Data Types tab.
  7. Click Import Data Object.
  8. Select the Java class that you created.
  9. Click Import.
  10. Check the type of the field into which the List field was converted.

Expected result: The field has the type collection.

Actual result: The field has the type Any.

Workaround: Manually change the type of the field to collection.

When you change a decision table header in the properties panel, the change is not saved [RHDM-1181]

Issue: In the DMN designer, when you edit a decision table you can click a header to view its properties panel. However, if you change settings for the header in the properties panel, the change is not saved.

Steps to reproduce:

  1. Edit a decision table in an element in the DMN designer.
  2. Click a header in the table.
  3. Change a field, such as Input expression, in the properties panel on the right side of the screen.

Expected result: The change is reflected in the table.

Actual result: The change is not reflected in the table.

Workaround: Click the header to view the pop-up window next to the header. Edit the settings in this window.

When you open a DMN diagram that does not contain layout information, nodes are all in the same position [RHDM-1150]

Issue: When you open a DMN model file and this file does not contain layout information, all DMN nodes are displayed in the same position.

Steps to reproduce:

  1. Open or create a project in Business Central.
  2. Import a DMN model file that does not contain layout information.

Expected result: The nodes are spread across the canvas.

Actual result: All nodes are in the same position.

Workaround: Click the automatic layout Automatic layout button in the toolbar.

5.4. Red Hat OpenShift Container Platform

Product environment fails to deploy on Amazon Web Services (AWS) with AWS Elastic Block Storage (EBS) because of AWS EBS volume plugin lack of support for ReadWriteMany (RWX) persistent volume access mode [RHPAM-2480]

Issue: Several templates used for installing Red Hat Decision Manager on Red Hat OpenShift Container Platform, as well as deployment of several environment types using the Business Automation operator, fail to deploy on AWS with EBS. The templates and environment types include persistent volume claims that require support for the ReadWriteMany access mode and the AWS EBS volume plugin does not provision persistent volumes with this access mode.

The rhdm76-authoring-ha.yaml template is affected.

Workaround: Deploy an NFS server and provision the persistent volumes using NFS. For information about provisioning persistent volumes using NFS, see one of the following guides:

OptaWeb Vehicle Routing tests fail due to different versions of dependencies [RHDM-1129]

Issue: OptaWeb Vehicle Routing is distributed with the incorrect package-lock.json file. As a result, snapshot tests of the optaweb-vehicle-routing-frontend module fail because of changes in HTML code generated by different versions of dependencies.

Workaround:

  1. Change directory to the optaweb-vehicle-routing-frontend module.
  2. Enter the following command to download the required dependencies:

    $ npm install
  3. Enter the following command to run the tests:

    $ npm test
  4. Press the u key to update failing snapshots.

5.5. Offline Maven repository

The offliner tool reports errors when it downloads artifacts for an offline Maven repository [RHPAM-2234]

Issue: When you run the offliner tool to download artifacts for an offline Maven repository, the tool reports that some artifacts failed to download. The error message is The artifact was not found in any of the provided repositories.

Workaround: If the failed artifacts relate to installer, ignore the error messages. These artifacts are not required for the offline Maven repository.

In other cases, for example, for maven-compiler-plugin or docbook artifacts, specify an additional repository and run the offliner command again:

java -jar offliner-<version>.jar -r https://maven.repository.redhat.com/ga/ -r https://repo1.maven.org/maven2/ -r https://repository.jboss.org/nexus/content/groups/public/ -d /home/user/temp rhdm-7.6.0-offliner.txt