Chapter 7. Known issues in Red Hat Decision Manager 7.11.0

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

7.1. Business Central

The Business Central web application continues to poll in an open browser after the server has stopped [RHPAM-3635]

Issue: When you keep the Business Central web application open in a browser window, after the KIE Server has stopped, it keeps on polling the endpoint of the previously running KIE Server.

Workaround: None.

In standalone editors, the setContent method implementation must receive path and content [RHPAM-3629]

Issue: In standalone editors, the setContent implementation must implement the setContent method defined in EditorAPI along with path and content parameters instead of content only.

Workaround: None.

When an executing model uses an imported inputs and decision nodes, you receive an error message [RHDM-1733]

Issue: The test scenario tool is unable to execute any models that use imported inputs and decisions nodes. The automatically generated decision table columns reflects the incorrect values.

Workaround: None.

Method calls do not support template keys [RHDM-1729]

Issue: If you remove one of the action calls from the Business Rule Language (BRL) action column, the generated DRL file is updated incorrectly.

Steps to reproduce:

  1. Import the Mortgages sample project.
  2. Replace the original content of LoanApplication with the [LoanApplication.java].
  3. Replace the original content of Pricing Loans with the Pricing loans (1).gdst file. (This file is attached in the [RHDM-1729] issue).
  4. Validate Pricing loans (1).gdst file.
  5. Go to the Columns tab and select Action columns.
  6. For the call functions option, click Edit.
  7. Remove Call [application.addExplanation] and Call [application.deadline] and click Finish.

Workaround: None.

The Business Rule Language (BRL) columns do not support the conversion of method call data types [RHDM-1696]

Issue: When a guided decision table is converted into an XLS decision table, the method calls with String or Date data type arguments are not converted correctly.

Steps to reproduce:

  1. Import the Mortgages sample project.
  2. Replace the original content of LoanApplication with the [LoanApplication.java].
  3. Replace the original content of Pricing Loans with the Pricing loans (1).gdst file. (This file is attached in the [RHDM-1696] issue).
  4. Convert the Pricing Loans into an XLS table.

  5. Open the converted XLS table and switch to the Source tab.

    The addExplanation method assumes exp is a variable instead of constant. The deadline method assumes 08-Mar-2021 is a date, but it is a string. Some wrapper modules are needed for converting String into Date.

Expected result: Validation of the XLS table succeeds.

Actual result: Validation of the XLS table fails.

Workaround: None.

The guided decision table sorting functionality does not work in the decision table graph [RHDM-1664]

Issue: The guided decision table sorting functionality does not work in the decision table graph. The merged view of the table is not sorted correctly.

Steps to reproduce:

  1. Import the Mortgages sample project.
  2. Import the second small table.gds file attached in the [RHDM-1664] issue.
  3. Create a decision table graph that contains the Pricing Loans column with the second small table.gds file.
  4. Try to sort the second small table.

Expected result: The guided decision table sorting functionality works correctly in the decision table graph.

Actual result: The guided decision table sorting functionality does not work correctly.

Workaround: None.

The guided decision table merged view throws an error [RHDM-1663]

Issue: The merged view of the guided decision table is not sorted properly. You receive an unexpected system error.

Workaround: None.

In the guided decision table, sorting functionality does not work for LocalDate attribute [RHDM-1662]

Issue: In the guided decision table, sorting functionality does not work for LocalDate attribute.

Workaround: None.

7.2. DMN designer

Unable to create a new .scesim file in a VSCode instance when a workspace contains multiple folders [RHPAM-3621]

Issue: When there are multiple folders within one workspace, the scenario simulation editor fails when creating a new scenario for a specific DMN model.

Steps to reproduce:

  1. Create a VSCode workspace with a single folder in it.
  2. Create a valid DMN file.
  3. Create a .scesim file for the newly created DMN file.
  4. Add a new folder in a VSCode workspace.
  5. Create a different .scesim file for the same DMN file.

Workaround: Keep a single folder inside your workspace. If you want to work on multiple projects, open the projects in separate VSCode instances.

A decision service is missing the encapsulatedDecisions element for transitive dependencies in a model with multiple decision requirements diagrams [RHDM-1732]

Issue: When a model contains multiple decision requirements diagrams (DRD) and tries to reuse a decision component by adding it into a decision service node, the resulting decision service node does not contain any encapsulatedDecisions definitions for its transitive dependencies.

Steps to reproduce:

  1. Define multiple DRDs.
  2. In one DRD, define some decisions with transitive dependency on a decision.
  3. In another DRD, define decision services and reuse the previously created decision component. Do not duplicate the transitive dependency.
  4. Build and deploy your project.

  5. Complete any of the following tasks:

    • Evaluate the decision to verify the error reported in the description.
    • Check the dmn source code and determine whether or not the inputData attribute from the decision service is missing.
    • Check the decision service details in the Properties panel.

Workaround: The transitive decisions must be part of the encapsulatedDecisions section of the modeled decision service.

DMN editor removes the edges for duplicate decision nodes on canvas [RHDM-1714]

Issue: An issue occurs with the edges, when you duplicate a decision component in a canvas. The edges that are originally modeled are either shifted or removed.

Steps to reproduce:

  1. Create two decision nodes, A and B, and link them.
  2. Drag the decision node A from the Decision Components panel on canvas.
  3. Create an input node and link it to the duplicated decision node A.
  4. Click Save.

  5. Reopen the project.

    The link from the input node is now connected to the original decision node A, while the duplicated decision node has no links at all.

Workaround: Keep a single occurrence of the decision component for each DRD.

In the DMN editor, the suggestion box does not parse the function arguments [RHDM-1661]

Issue: The the DMN editor does not parse any helpful suggestions when you are writing literal expressions.

Steps to reproduce:

  1. Open a DMN editor.
  2. Add a decision node.
  3. Set the expression as Literal expression.
  4. Enter the date(2011 | , , ) expression and check the suggestion box.

Expected result: The DMN editor provides helpful suggestions when you are writing literal expressions.

Actual result: The DMN editor does not parse any helpful suggestions when you are writing literal expressions.

Workaround: None.

In the DMN editor, the suggestion box parses the results of an addition expression as a list instead of a number [RHDM-1660]

Issue: When you parse an addition expression to a literal expression, the DMN editor suggests functions that return list instead of a number.

Steps to reproduce:

  1. Open a DMN editor.
  2. Add a decision node.
  3. Set the expression as Literal expression.
  4. Enter the sum([1]) + sum([2]) expression and check the suggestion box.

Expected result: The DMN editor suggests correct functions for an addition expression.

Actual result: The DMN editor suggests functions that return list instead of a number.

Workaround: None.

In the DMN editor, the suggestion box fails to recognize variables [RHDM-1658]

Issue: When you parse the number type to a literal expressions, the DMN editor fails to recognize variables.

Steps to reproduce:

  1. Open a DMN editor.
  2. Add a decision node.
  3. Set the expression as Literal expression.
  4. Enter the numeric variable + expression and check the suggestion box.

Expected result: The DMN editor recognizes variables when you parse the number type to a literal expressions.

Actual result: The DMN editor fails to recognize variables.

Workaround: None.

In the DMN editor, the suggestion box fails to recognize the duration expression [RHDM-1656]

Issue: When you try to parse the duration expression, the DMN editor suggests string functions instead of duration functions.

Steps to reproduce:

  1. Open a DMN editor.
  2. Add a decision node.
  3. Set the expression as a Literal expression.
  4. Enter the date( "2012-12-25" ) - date( "2012-12-24" ) expression and check the suggestion box.

Expected result: The DMN editor recognizes the duration expression.

Actual result: The DMN editor fails to recognize the duration expression and suggests string functions.

Workaround: None.

In the DMN editor, the suggestion box fails to recognize date expressions [RHDM-1654]

Issue: When you try to parse a date expression, the DMN editor suggests string functions instead of date functions.

Steps to reproduce:

  1. Open a DMN editor.
  2. Add a decision node.
  3. Set the expression as Literal expression.
  4. Enter the date(date and time( "2012-12-25T11:00:00Z" )) expression and check the suggestion box.

Expected result: The DMN editor recognizes the date expressions.

Actual result: The DMN editor fails to recognize the date expression and suggests string functions instead of date functions.

Workaround: None.

In the DMN editor, the suggestion box fails to recognize a negated boolean expression [RHDM-1652]

Issue: When you try to parse a negated boolean expression, the DMN editor offers different suggestions which are not related to the expression.

Steps to reproduce:

  1. Open a DMN editor.
  2. Add a decision node.
  3. Set the expression as Literal expression.
  4. Enter a false or not false expression and check the suggestion box.

Expected result: The DMN editor offers related suggestions when you parse a negated boolean expression.

Actual result: The DMN editor fails to provide related suggestions when you parse a negated boolean expression.

Workaround: None.

7.3. Red Hat build of Kogito

From given asset, wrong archetype is used to generate project [RHPAM-3654]

Issue: When you upload an asset as a source for KogitoBuild, the Red Hat build of Kogito S2I image generates the project using kogito-quarkus-archetype:1.5.1-SNAPSHOT. It is expected to use the kogito-quarkus-dm-archetype:1.5.0.redhat-00001.

Steps to reproduce:

  1. Install the RHPAM Kogito Operator.

  2. Create a KogitoBuild as follows: 

    apiVersion: rhpam.kiegroup.org/v1
kind: KogitoBuild
metadata:
  name: example-quarkus-local
spec:
  buildImage: >-
    registry-proxy.engineering.redhat.com/rh-osbs/rhpam-7-rhpam-kogito-builder-rhel8:7.11.0-1
  runtimeImage: >-
    registry-proxy.engineering.redhat.com/rh-osbs/rhpam-7-rhpam-kogito-runtime-jvm-rhel8:7.11.0-3
  type: LocalSource

  3. Upload an asset to the Red Hat OpenShift Container Platform using Red Hat OpenShift Container client as follows: 

    oc start-build example-quarkus-local-builder --from-file=https://github.com/kiegroup/kogito-examples/blob/stable/dmn-quarkus-example/src/main/resources/Traffic%20Violation.dmn
  4. Check the builder log file.

Expected result: When you upload an asset for KogitoBuild, the Red Hat build of Kogito S2I image generates the project using kogito-quarkus-dm-archetype:1.5.0.redhat-00001.

Actual result: When you upload an asset for KogitoBuild, the Red Hat build of Kogito S2I image generates the project using kogito-quarkus-archetype:1.5.1-SNAPSHOT.

Workaround: None.