Red Hat Summit Red Hat SummitSuporteConsoleDesenvolvedoresComeçar um testeContato

Este conteúdo não está disponível no idioma selecionado.

Chapter 5. Known issues

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

5.1. Business Central
Copiar o link

You cannot upload a spreadsheet that contains a large decision table [RHDM-488]

Issue: If you try to upload a spreadsheet that contains a large decision table into Business Central, an out-of-memory error appears in the error.log file.

Steps to reproduce:

  1. Create a spreadsheet that contains a large decision table.
  2. Create a new project in Business Central.
  3. Click Add Asset and then select Spreadsheet Decision Table.
  4. Attach the spreadsheet that contains the large decision table.
  5. Review the server error.log file.

Actual result: An out-of-memory error appears in the error.log file.

Workaround: None.

An unexpected error occurs if you delete a project that contains a business process [RHPAM-1943]

Issue: If you delete a project that contains a business process, an unexpected error occurs.

Steps to reproduce:

  1. Create a project in Business Central.
  2. Add a business process asset to the project.
  3. Save the business process asset.
  4. Delete the business process asset.

Expected result: The business process asset is deleted.

Actual result: An error occurs.

Workaround: None.

The palette of an existing process is not in sync with project settings changes [RHPAM-1925]

Issue: If you enable or disable a service task in the Administration page or install or uninstall a service task in the project’s settings Service tasks section, when you open the process the palette displays the original state of the service task. If you install a service task, the service task is not shown in the palette. If you uninstall a service task, the service task is still shown in the palette.

Steps to reproduce:

  1. Create a project.
  2. Create a process called P1.
  3. In the project’s settings, install a new service task.
  4. Create a process called P2.
  5. Verify that the service task is present in the palette of process P2.
  6. Create a process using the newly added task.
  7. Go to process P1.
  8. Examine the palette and observe that the service task is not available.
  9. Go to the project’s settings and uninstall the service task.
  10. Go to process P2.
  11. Examine the palette and observe that the service task is still present in the diagram and available in the palette.

Expected result: The palette reflects the state of the process.

Actual result: The palette is out of sync with the state of the process.

Workaround: After you install or uninstall an item in the service repository, close and reopen the process designer editor.

5.2. Installer
Copiar o link

The controller URL is not updated in the standalone.xml file if only Process Server is installed [RHPAM-1781]

Issue: When you run the Red Hat Process Automation Manager installer and you specify a URL for the controller, the URL is not updated in the Red Hat JBoss EAP standalone.xml and standalone-full.xml files.

Steps to reproduce:

  1. Run the Red Hat Process Automation Manager installer.
  2. Specify an Red Hat JBoss EAP installation for container.
  3. Select only Process Server to install.
  4. Select Advanced Configuration and update controller URL.
  5. Complete the installation.
  6. Open the Red Hat JBoss EAP standalone.xml or standalone-full.xml file and find the controller URL.

Expected result: The value of the controller URL property is the URL that you entered during installation.

Actual result: The value of the controller URL property is the default value.

Workaround: Manually update the value of the controller URL property in the Red Hat JBoss EAP standalone.xml and standalone-full.xml file.

5.3. Process Server
Copiar o link

You cannot deploy a KJAR with a PMML asset to a Process Server Spring Boot starter on Windows [RHDM-852]

Issue: If a KJAR contains a PMML asset, you cannot deploy it as a container on a Process Server that is running in the kie-server-spring-boot-starter Spring Boot starter on Microsoft Windows.

Steps to reproduce:

  1. Create a KJAR that contains a PMML asset.
  2. Start kie-server-spring-boot-starter on Windows.
  3. Deploy the KJAR to a Process Server that is running the kie-server-spring-boot-starter Spring Boot starter on Microsoft Windows.

Expected result: The KJAR is deployed successfully.

Actual result: The KJAR cannot be deployed.

Workaround: None.

5.4. OpenShift
Copiar o link

User password is displayed in the Readiness and Liveness probes [RHPAM-1829]

Issue: If you deploy Red Hat Process Automation Manager on OpenShift, the user password is displayed in both the Readiness and Liveness probes.

Workaround: None.

5.5. Red Hat Business Optimizer
Copiar o link

ScoreCalculationCountLimit termination does not work with multi-threaded solving [RHDM-740]

Issue: Red Hat Business Optimizer configured with the score calculation count termination (ScoreCalculationCountLimit) does not terminate. The score calculation count termination is primarily used for testing.

Workaround: Use another type of termination.

Red Hat logoGithubredditYoutubeTwitter

Aprender

Experimente, compre e venda

Comunidades

Sobre a documentação da Red Hat

Ajudamos os usuários da Red Hat a inovar e atingir seus objetivos com nossos produtos e serviços com conteúdo em que podem confiar. Explore nossas atualizações recentes.

Tornando o open source mais inclusivo

A Red Hat está comprometida em substituir a linguagem problemática em nosso código, documentação e propriedades da web. Para mais detalhes veja o Blog da Red Hat.

Sobre a Red Hat

Fornecemos soluções robustas que facilitam o trabalho das empresas em plataformas e ambientes, desde o data center principal até a borda da rede.

Theme

© 2026 Red HatVoltar ao topo