Chapter 8. Known issues in Red Hat Process Automation Manager 7.8.1

This section lists known issues with Red Hat Process Automation 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:

  1. In Business Central, go to Menu → Deploy → Execution Servers.
  2. Under Deployment Units, click Add Deployment Unit.
  3. Enter the non existent 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 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:

  1. In Business Central, go to Menu → Deploy → Execution Servers.
  2. Under Deployment Units, click Add Deployment Unit.
  3. Enter the non existent GAV values manually.
  4. Select the Start Deployment Unit? check box to start the service.
  5. Click Finish.
  6. 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:

  1. In Business Central, go to Menu → Design → Projects.
  2. Click Try samples.
  3. Open Traffic_Violation project.
  4. Open Traffic Violation DMN file and select Data Types tab.
  5. To modify the tViolation data type, click tViolation.
  6. To add the constraints to the tViolation data type, click the edit icon, click Add Constraints.
  7. Select Enumeration from the Select constraint type pull-down menu and add 50, 90, and, 130 in the fields.
  8. Click OK, then click the check mark to the right of the tViolation data type to save your changes.
  9. Click Save and close the DMN editor.
  10. Open Violation Scenarios test scenario.

    You receive Wrong column mapping error pop-up.

Workaround:

  1. From the Test Scenario designer toolbar on the upper-right, click Export and export the .CSV file.
  2. Click the affected property column header.
  3. Select the property from the Test Tools panel again.
  4. Confirm the pop-up to delete the values.
  5. Import the originally exported .CSV file.

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:

  1. Open Business Central.
  2. Open any project.
  3. Create a data object.
  4. In the Source tab of a data object, change the package name.
  5. Click Save.
  6. In the Information alert window, click + Yes, Move and confirm the changes.

    You see Item successfully renamed notification.

  7. Close the editor.

    You receive Unsaved changes error.

Workaround: None.

8.2. Process designer

Case management properties are missing in a case definition [RHPAM-3131]

Issue: In Properties panel, case management properties are missing in a case definition.

Steps to reproduce:

  1. Create a case project.
  2. Create a case definition.
  3. Open Properties panel and add any case management property.

Expected result: Case management section is present in Properties panel.

Actual result: Case management section is not present in Properties panel.

Workaround: Set the Adhoc property to true. To reflect the changes, save your changes, close the case and reopen the Properties panel.

8.3. Installer

On Red Hat JBoss EAP, the Red Hat Process Automation Manager installer adds an additional $ sign in the vaulted password of database user [RHPAM-3148]

Issue: When you use graphical user interface, installer adds an additional $ sign in the vaulted password for KIE Server data source and connection to the database fails.

Steps to reproduce:

  1. Install KIE Server on Red Hat JBoss EAP using graphical user interface.
  2. Configure data source properties for KIE Server.
  3. Complete the installation and run the container.

    You receive an error regarding incorrect login credentials on start up in logs.

Expected result: No additional $ sign in the vaulted password and KIE Server is connecting to the database.

Actual result: There is an additional $ sign in the vaulted password and KIE Server is not connecting properly to the database.

Workaround:

  1. Open the standalone-full.xml file in your Red Hat JBoss EAP directory.
  2. Search the following element in your data source definition:

    <subsystem xmlns="urn:jboss:domain:datasources:5.0">
  3. Search for <security> element.

    <password> $${VAULT::datasource.NAME::password::1}</password>
  4. Remove an additional $ sign in the vaulted password and the datasource element in the standalone-full.xml file should look similar to the following:

    <password> ${VAULT::datasource.NAME::password::1}</password>

When you are auto installing Red Hat Process Automation Manager on Red Hat JBoss EAP, Red Hat Process Automation Manager installer tries to configure properties for Red Hat JBoss Web Server [RHPAM-3150]

Issue: Red Hat Process Automation Manager installer tries to configure properties for Red Hat JBoss Web Server when you are auto installing on Red Hat JBoss EAP. Automated installer is not checking the conditions and executing Red Hat JBoss Web Server related steps even though the users are using installation script with Red Hat JBoss EAP.

Steps to reproduce:

  1. Run Red Hat Process Automation Manager installer with the default options.
  2. Use Red Hat JBoss EAP as an installation container.
  3. Complete the installation, generate an installation script, and name it as auto.xml.
  4. Clean the used Red Hat JBoss EAP container and run the installation again using the generated installation script:

    java -jar rhpam-installer-7.8.x.jar auto.xml -variables rhpam.username=rhbaUser,rhpam.password=bpmsAdmin123$
  5. Run the installed Red Hat Process Automation Manager.

Expected result: Red Hat Process Automation Manager installer is not trying setup any Red Hat JBoss Web Server related properties and installation on Red Hat JBoss EAP using automated script succeeds.

Actual result: Red Hat Process Automation Manager installer tries to setup Red Hat JBoss Web Server related properties and installation on Red Hat JBoss EAP using automated script fails.

Workaround: Install manually. Do not use the generated script for Red Hat JBoss EAP.

8.4. Form modeler

Document upload feature does not work on Windows [RHPAM-3117]

Issue: In Windows, with the Document form field, you cannot upload documents that are required as part of a form or process.

Steps to reproduce:

  1. Set the document marshalling strategy.
  2. Create a document variable in a business process.
  3. Map the task inputs and outputs to the document variable.

Expected result: Document upload feature is working on Windows.

Actual result: Document upload feature is not working on Windows.

Workaround: None.

8.5. Red Hat OpenShift Container Platform

S2I build ignores Java virtual machine (JVM) properties [RHDM-1419]

Issue: S2I build fails because the KJAR files and its dependencies are uploaded in Nexus which are accessible via HTTPS and they are signed by a self-signed certificate.

Workaround: None.