Chapter 5. Known issues

This section lists known issues with Red Hat Process Automation 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 Deployments → General 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 Deploy → Execution 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 Process Automation 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 Process 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 Process 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 Process Server is switched from development mode into production mode, Business Central does not recognize the change.

Steps to reproduce:

  1. Ensure a Process Server is connected to Business Central and set to development mode.
  2. Shut down the Process Server.
  3. Reconfigure the Process Server to use production mode. Do not change other configuration settings.
  4. Start the Process 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.

When you save a filter and then activate it, an error message displays [RHPAM-2545]

Issue: When you save a filter and immediately after this action activate it from the Saved filters view, an error message displays.

Steps to reproduce:

  1. Open the Manage Process Instances perspective.
  2. Configure a quick filter.
  3. Save the filter.
  4. Click the maximize button Saved filters dock icon.
  5. Click the new filter to activate it.

Expected result: The filter is activated.

Actual result: An Unexpected system error message displays. The filter is activated.

Workaround: none.

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. Process designer

Validation for a signal name fails if the name includes spaces, colons (:), or other special characters [RHPAM-2557]

Issue: In the process designer, the validation for a signal name fails if the name includes spaces, colons (:), or other special characters.

Steps to reproduce:

  1. Open a BPMN project in the process designer.
  2. Add a signal node on the canvas.
  3. In the Properties panel for the node, expand Implementation/Execution.
  4. Click the Signal drop-down list and select New.
  5. In the Signal field, enter Milestone 2: Order shipped.
  6. Press Tab on the keyboard to switch to the next field.

Expected result: The field content is saved successfully.

Actual result: The field contains the text without the spaces that you entered, Milestone2:Ordershipped and an Invalid characters error message appears.

Workaround: Use signal names that contain only letters, numbers, and the underscore character (_).

Note

If you import or migrate a project to the new process designer and any signal name in the project contains spaces or special characters, a warning displays. You can ignore the warning because the execution of the project is not affected.

If the process designer Properties panel is open and you maximize and then restore the panel, it closes [RHPAM-2613]

Issue: If the process designer Properties panel is open and then you maximize and restore the panel, it closes.

Steps to reproduce:

  1. Open the process designer.
  2. In the process designer, create and save a business process.
  3. Open the process designer Properties panel.
  4. Click the maximize button Maximize button to maximize the process designer panel to the size of the entire screen.
  5. Click the minimize button Minimize button to restore the process designer panel to its previous size.

Expected result: The Properties panel remains open.

Actual result: The Properties panel is closed.

Workaround: Open the Properties panel again.

If the process designer Properties panel is open and you switch to a different view, the panel closes [RHPAM-2612]

Issue: If the process designer Properties panel is open and you switch to a different view, the panel closes.

Steps to reproduce:

  1. Open the process designer.
  2. In the process designer, create and save a business process.
  3. Open the process designer Properties panel.

  4. Switch the view in one of the following ways:

    • Click the process name in the breadcrumb trail in the top part of the window and then select the business process asset again.
    • Click the process in a drop-down menu and then select the business process asset again.
    • Switch to the Documentation tab and then switch back to the Model tab.

Expected result: The Properties panel remains open.

Actual result: The Properties panel is closed.

Workaround: Open the Properties panel again.

When you create a gateway, no options are available from the Default Route drop-down list in the Properties panel [RHPAM-2536]

Issue: In some cases, when you create a gateway no options are available from the Default Route drop-down list in the Properties panel.

Steps to reproduce:

  1. Create a process with a parallel gateway.
  2. Append several nodes to the parallel gateway.
  3. Convert the parallel gateway into an exclusive gateway.
  4. Select the gateway and click the Default Route option in the Properties panel.

Expected result: The drop-down list contains all of the nodes that follow the gateway.

Actual result: The drop-down list is empty.

Workaround: Deactivate the gateway and activate it again. Alternatively, save and reopen the process.

If you try to migrate a process with a sequence flow without the source and target nodes set, you should receive a warning message, but you do not [RHPAM-2453]

Issue: If a process in the legacy process designer contains a sequence flow without the source and target nodes set, and you try to migrate that process to the new process designer, you should receive a warning message, but you do not. It is also not possible to migrate process.

Steps to reproduce:

  1. Create a process in the legacy process designer.
  2. Add a sequence flow to the process, do not set the source and target nodes, and then save the process.
  3. Click the Migrate button.

Expected result: You see a message telling you that the source and target nodes for a sequence flow are not set and you cannot migrate the process.

Actual result: No message appears and you cannot migrate the process.

Workaround: None.

If you migrate a process from the legacy process designer to the new process designer, you receive an incorrect warning that a node will be ignored [RHPAM-2452]

Issue: If you migrate a process from the legacy process designer to the new process designer, you receive a warning that a node will be ignored. However, the node is not ignored and is migrated successfully.

Steps to reproduce:

  1. Create a Start to End process in the legacy process designer.
  2. Migrate the process to the new process designer.

Expected result: No warning about ignoring elements are shown if no elements will be ignored after migration.

Actual result: Warnings are shown that some unknown element will be ignored.

Workaround: Ignore the warnings and confirm that all nodes migrate successfully.

In the new process designer, the warning message for migrating a Group element is missing [RHPAM-2454]

Issue: If you migrate a process that contains a Group element from the legacy process designer to the new process designer, the warning message about ignoring the node is missing.

Steps to reproduce:

  1. Create a process in the legacy process designer.
  2. Add a Group element to the process and then save the process.
  3. Migrate the process from the legacy process designer to the new process designer.

Expected result: You see a warning message about ignoring the node.

Actual result: You do not see the warning message.

Workaround: None.

5.5. Process instance migration

The process instance migration service does not work with an Oracle database [RHPAM-2558]

Issue: The process instance migration service fails to start when it is configured to use an Oracle database.

Steps to reproduce:

  1. Configure the process migration service to use an Oracle database.
  2. Start the process migration service.

Expected result: The process migration service starts.

Actual result: The process migration service fails to start.

Workaround: Configure the process migration service to use a database on a non-Oracle database server.

5.6. 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 Process Automation 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 following templates are affected:

  • rhpam76-managed.yaml
  • rhpam76-prod.yaml
  • rhpam76-prod-immutable-monitor.yaml
  • rhpam76-authoring.yaml
  • rhpam76-authoring-ha.yaml

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.7. 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 rhpam-7.6.0-offliner.txt