Red Hat Summit 红帽全球峰会支持控制台（Console）开发人员开始试用联系人

此内容没有您所选择的语言版本。

Chapter 5. Known issues

This section lists known issues with Red Hat Process Automation Manager 7.4.

5.1. Business Central
复制链接

Guided rules expose parentheses outside of an expression [RHDM-1046]

Issue: When you create a guided rule, if you select the field for multiple values and each value is enclosed in parenthesis, for example (red), (blue), an invalid rule is generated.

Steps to reproduce:

  1. Open Business Central.
  2. Open any project.
  3. Create the data object Car with the field color:String.
  4. Create a new guided decision table.

  5. Define a new Condition column:

    Pattern: $c : Car

    Calculation Type: Literal value

    Field: color

    Operator: is contained in the (comma separated) list

    Header: Car color is

  6. Select the Model tab and enter (red), (blue) in the corresponding cell.

Expected result: The $c : Car(color in ("(red)", "(blue)")) rule is generated.

Actual result: The $c : Car( color in ("red)", "(blue") ) rule is generated.

Workaround: In the Model tab, enter the values as shown in the following example: 

((red), (blue))
Copy to Clipboard Toggle word wrap

A guided scorecard cannot be tested with the Test Scenario (Legacy) asset [RHPAM-2307]

Issue: If a guided scorecard name begins with a lowercase letter, you cannot test the scorecard with the Test Scenario (Legacy) asset.

Steps to reproduce:

  1. Create a guided scorecard with a name that begins with a lowercase letter.
  2. Import the guided scorecard into Business Central.
  3. Click Test.

Expected result: The test completes successfully.

Actual result: The test fails.

Workaround: Make sure that guided scorecard names do not begin with lowercase letters.

You cannot add a new group in Business Central integrated with RH-SSO [RHPAM-2036]

Issue: The following exception occurs when you try to add a new group in Business Central if Business Central is integrated with RH-SSO 7.3.0: 

java.lang.NoSuchMethodError:org.keycloak.representations.idm.RoleRepresentation.setScopeParamRequired(Ljava/lang/Boolean;)
Copy to Clipboard Toggle word wrap

Steps to reproduce:

  1. Open Business Central.
  2. Open the Admin page.
  3. Open Groups.
  4. Try to create a new group.

Expected result: The new group is created.

Actual result: A dialog box with the listed exception appears.

Workaround: Add the group in RH-SSO instead of adding it in Business Central.

When you create an asset, the package drop-down button does not appear immediately [RHPAM-2133]

Issue: When you create an asset, the package drop-down button is invisible and an error about package selection appears.

Steps to reproduce:

  1. Create a project in Business Central.
  2. Try to create a business process.

Expected result: The package drop-down button is visible and you can create the business process.

Actual result: The package drop-down button is initially invisible and it appears after several seconds.

Workaround: Wait until the package drop-down button is visible or reopen the dialog window for asset creation.

5.2. Process designer
复制链接

Human task comments are not retained when a process instance is finished [RHPAM-2258]

Issue: Human task comments are retained and visible only while the respective process instance is running. When the process instance is completed or aborted, comments from human tasks disappear even though the tasks are still visible in Business Central.

Steps to reproduce:

  1. Start a process instance with two consecutive human tasks.
  2. Comment on the first human task.
  3. Claim, start, and complete the first task.
  4. Check the Comments tab of the human task to confirm that the comments are retained for the completed task.
  5. Abort the process instance or complete the task preventing the instance from finishing.
  6. Navigate to the log file for the first task again.

Expected result: Data about the first task is available in the Comments tab of the human task .

Actual result: The first task is still available in Business Central but no data is available in the log file.

Workaround: None.

Greater than (>) and less than (<) symbols in data types break a process [RHPAM-2193]

Issue: If you place greater than (>) and less than (<) symbols in a data type for a process variable, you cannot reopen the process. The XML editor appears instead.

Steps to reproduce:

  1. Create a process and add the list1:java.util.List<String> process variable.
  2. Save and reopen the process.

Expected result: The process opens.

Actual result: The process does not open.

Workaround: None.

If a case task actor is invalid, the resulting BPMN file is also invalid [RHPAM-2240]

Issue: The new process designer sometimes generates an invalid XML file. A user task with an actor assigned is generated as a a potentialOwner element in the XSD file. 

<bpmn2:potentialOwner id="5058b718-8866-4ccd-b793-d5ebf48de5a2">
<bpmn2:resourceAssignmentExpression id="_gN_feI4_Eem2-an8Fwu06w">
<bpmn2:formalExpression id="_gN_feY4_Eem2-an8Fwu06w">manager</bpmn2:formalExpression>
</bpmn2:resourceAssignmentExpression>
</bpmn2:potentialOwner>
Copy to Clipboard Toggle word wrap

The id of the potentialOwner element is missing an underscore at the beginning, which means that if the first element is a number, this is now an invalid ID.

Tasks that have ioSpecification should always define an inputSet and outputSet, even if those are empty.

Steps to reproduce:

Create a user task with no output mapping. This will generate the following output: 

<bpmn2:ioSpecification id="_rEnOQY5AEem2-an8Fwu06w">
<bpmn2:dataInput id="38B29C0C-6BD8-4275-ACCE-D5D97DEBB2CB_TaskNameInputX" drools:dtype="Object" itemSubjectRef="_38B29C0C-6BD8-4275-ACCE-D5D97DEBB2CB_TaskNameInputXItem" name="TaskName"/>
<bpmn2:dataInput id="38B29C0C-6BD8-4275-ACCE-D5D97DEBB2CB_SkippableInputX" drools:dtype="Object" itemSubjectRef="_38B29C0C-6BD8-4275-ACCE-D5D97DEBB2CB_SkippableInputXItem" name="Skippable"/>
<bpmn2:inputSet id="_rEnOQo5AEem2-an8Fwu06w">
<bpmn2:dataInputRefs>_38B29C0C-6BD8-4275-ACCE-D5D97DEBB2CB_TaskNameInputX</bpmn2:dataInputRefs>
<bpmn2:dataInputRefs>_38B29C0C-6BD8-4275-ACCE-D5D97DEBB2CB_SkippableInputX</bpmn2:dataInputRefs>
</bpmn2:inputSet>
</bpmn2:ioSpecification>
Copy to Clipboard Toggle word wrap

Expected result: The output includes an empty outputSet attribute.

Actual result: The output does not include an outputSet attribute.

Workaround: None.

Nodes and distribution lines do not fully align horizontally [RHPAM-2241]

Issue: It is difficult to precisely align some nodes horizontally.

Steps to reproduce:

  1. Create a process.
  2. Try to align a node and connector horizontally.

Expected result: The node and connector are aligned.

Actual result: The node and connector are not aligned.

Workaround: None.

The multiple instance properties of a multiple instance subprocess are not visible for nodes inside of a multiple instance subprocess [RHPAM-2257]

Issue: If you model a process with a multiple instance subprocess as a multiple instance node, the multiple instance Data Input and multiple instance Data Output variables are not visible for nodes inside of the multiple instance subprocess.

Steps to reproduce:

  1. Create a multiple instance subprocess for execution by selecting the multiple instance collection input/output from an existing process level list and setting new variables for multiple instance data input and output.
  2. Add a user task inside of the multiple instance subprocess.
  3. Try to configure a user task so that is uses multiple instance data input/output.

Expected result: The new variables for multiple instance data input and output are listed in the data I/O editor Source and Target fields and you can use the new variables for multiple instance data input and output.

Actual result: The new variables for multiple instance data input and output are not listed in the data I/O editor Source and Target fields.

Workaround: To use variables for multiple instance data input and output, define them in Process Data Process Variables before creating the multiple instance subprocess for execution.

Data output associations do not work correctly when they are declared twice [RHPAM-2242]

Issue: If the data output variable associated with a user task is declared twice, it is not stored in the resulting XML file.

Steps to reproduce:

  1. In Business Central, create a user task.
  2. Open the Properties panel.
  3. Expand the Implementation/Execution section.
  4. Click Assignments.
  5. In the Data Outputs and Assignment area, add a data output variable twice by using the same variable name.

Expected result: Two variables with the same name are stored in the BPMN XML file.

Actual result: The variables are not stored in the resulting BPMN XML file (XML) so when the process runs or loads, the data output assignments are missing.

Workaround: None.

5.3. Process engine
复制链接

Task operations are slow [RHPAM-2259]

Issue: Task operations such as Start, Complete, or Claim are noticeably slower when the Process Server API or UserTaskService is used. This issue appeared when a join was added to the getTaskInstanceById query. The performance of these operations will be restored to the previous state in a future patch release.

5.4. Process Server
复制链接

Query-related operations return errors when Process Server runs on either Red Hat JBoss Web Server or SpringBoot with DB2 [RHPAM-2292]

Issue: Query-related operations return errors when Process Server runs on either Red Hat JBoss Web Server or SpringBoot with DB2.

Steps to reproduce:

  1. Create a query-definitions.json file that contains content similar to the following example and add it to Process Server on Red Hat JBoss Web Server: 

    [
  {
    "query-name" : "first-query",
    "query-source" : "${org.kie.server.persistence.ds}",
    "query-expression" : "select * from ProcessInstanceLog",
    "query-target" : "PROCESS"

  }
]
    Copy to Clipboard Toggle word wrap
  2. Start Process Server. Process Server tries to register the new default query.

Expected result: The default query is successfully registered.

Actual result: An error code is returned, for example: 

com.ibm.db2.jcc.am.XaException: [jcc][t4][10401][12066][4.24.92]
XA exception: XAER_OUTSIDE ERRORCODE=-4228, SQLSTATE=null
Copy to Clipboard Toggle word wrap

Workaround: For Red Hat JBoss Web Server, set defaultAutoCommit=false in the XADataSource. For SpringBoot, set spring.datasource.defaultAutoCommit=false in application properties. This property must be added to the Narayana data source.

5.5. Red Hat OpenShift Container Platform
复制链接

Validation sub-element is missing for data sources [RHPAM-2226]

Issue: If you create a custom template for deploying Process Server on Red Hat OpenShift Container Platform and the server uses a MySQL or PostgreSQL database, Process Server data sources do not contain the validation sub-element where connection checkers and exception sorters are defined.

Steps to reproduce:

  1. Create a custom template for deploying Process Server on Red Hat OpenShift Container Platform with a MySQL or PostgreSQL database.
  2. View the contents of the template file.

Expected result: The template contains the expected data sources.

Actual result: The template does not contain the expected data sources.

Work around:

Add the following environment variables and values to your templates:

  • For MySQL: 

    name: RHPAM_CONNECTION_CHECKER
value: "org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLValidConnectionChecker"
name: RHPAM_EXCEPTION_SORTER
value: "org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLExceptionSorter"
    Copy to Clipboard Toggle word wrap

  • For PostgreSQL: 

    name: RHPAM_CONNECTION_CHECKER
value: "org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"
name: RHPAM_EXCEPTION_SORTER
value: "org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"
    Copy to Clipboard Toggle word wrap

5.6. Test scenarios
复制链接

Test scenarios designer can not access the parent data object fields [RHDM-1014]

Issue: Test scenarios designer cannot access a parent data object field, even if the field has public getter and setter attributes.

Steps to reproduce:

  1. Create a scenario with a field that is declared in the parent class.
  2. Run the scenario.
  3. Click View Alerts and review any alerts.

Expected result: The scenario runs successfully.

Actual result: The scenario fails because it cannot access the data object in the parent class.

Workaround: Include the data object in the child class.

Rule-based test scenarios that contain maps of simple types fail [RHDM-1015]

Issue: All rule-based test scenarios that contain a map of simple types as a cell value, for example Map<String or String, fail.

Steps to reproduce:

  1. Create a scenario.
  2. Create a map with a simple type value, for example Map<String, String>.
  3. Run the scenario.

Expected result: The scenario runs successfully.

Actual result: The scenario fails.

Workaround: None.

返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务，以及可以信赖的内容，帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情，请参阅红帽博客.

關於紅帽

我们提供强化的解决方案，使企业能够更轻松地跨平台和环境（从核心数据中心到网络边缘）工作。

Theme

© 2025 Red Hat