Chapter 8. Known issues in Red Hat Decision Manager 7.13.1

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

8.1. Business Central

Unable to deploy Business Central using JDK version 11.0.16 [RHPAM-4497]

Issue: It is not possible to deploy Business Central if your installation uses JDK version 11.0.16.

Actual result: Business Central does not deploy when launched.

Expected result: Business Central deploys successfully.

Workaround: Use a previous JDK version such as 11.0.5 or earlier.

8.2. Form Modeler

Date type process variable is empty when the process is started using Business Central form with the showTime set to false [RHPAM-4514]

Issue: When you use the default form rendering in Business Central and the process variable field has showTime=false, the started process instance shows that the variable is empty. The affected types are java.time.LocalDateTime, java.time.LocalDate, java.time.LocalTime, and java.util.Date.

Steps to reproduce:

  1. Define the process variable with a specific type.
  2. Generate a form.
  3. Open a form and set showTime=false for a specified field.
  4. Deploy the project.
  5. Open the process form.
  6. Specify the value in the process form.
  7. Check the process instance variables. The value for the specified variable is empty.

Workaround: None.

Form in KIE Server with a java.util.Date field does not allow the time to be inserted [RHPAM-4513]

Issue: When a process has a variable of type java.util.Date, the generated form, if the showTime attribute is true, does not allow inserting the time part. Then after submitting the Date variable shows all zeros in the time part of the datatype.

Workaround: None.

8.3. Red Hat OpenShift Container Platform

PostgreSQL 13 Pod won’t start because of an incompatible data dirctory [RHPAM-4464]

Issue: When you start a PostgreSQL pod after you upgrade the operator, the pod fails to start and you receive the following message:

Incompatible data directory. This container image provides PostgreSQL '13', but data directory is of version '10'. This image supports automatic data directory upgrade from '12', please carefully consult image documentation about how to use the '$POSTGRESQL_UPGRADE' startup option.

Workaround:

  1. Check the version of PostgreSQL: 

    $ postgres -V

  2. If the PostgreSQL version returned is 12.x or earlier, upgrade PostgreSQL:

    Red Hat Decision Manager versionPostgreSQL versionUpgrade instructions

    7.13.1

    7.10

    Follow the instructions in Upgrading database (by switching to newer PostgreSQL image version) to upgrade to PostgreSQL 12.x.

    7.13.2

    7.10

    1. Follow the instructions in Upgrading database (by switching to newer PostgreSQL image version) to upgrade to PostgreSQL 12.x.

    2. Follow the instructions in Upgrading database (by switching to newer PostgreSQL image version) to upgrade to PostgreSQL 13.x.

    7.13.2

    7.12

    Follow the instructions in Upgrading database (by switching to newer PostgreSQL image version) to upgrade to PostgreSQL 13.x.

  3. Verify that PostpreSQL has been upgraded to your required version: 

    $ postgres -V