Add a JR template for the report

Oct 13, 2025 by thesweetdesigns.com 128 views

ETP-1284 : Button List in Process Definition with JR Report Template Does Not Work

In the realm of process management, the ability to customize and extend the functionality of process definitions is crucial. However, a peculiar issue has been observed in the context of Report-type Process Definitions, which utilize JR templates. When a Button List is added to such a process definition, the default buttons mysteriously disappear, and the custom buttons generated by the Button List fail to function as expected. This article delves into the details of this issue, provides a step-by-step guide to reproduce the error, and outlines the expected behavior and solution design.

In a Process Definition with Report (using JR templates), when a Button List is added, the default buttons of this type of process definition disappear. Additionally, the buttons generated by the Button List do not function correctly because the system expects the default buttons to be present. No explicit error message is displayed, but issues can be observed in DevTools.

To reproduce the error, follow these steps:

Create a Process Definition of type Report (using JR templates): Navigate to the process management interface and create a new process definition. Select the Report type and choose JR templates as the report engine.
Add a JR template for the report: Create a new JR template for the report by clicking on the "Add Report" button. Configure the template as desired.
Configure a Button List in the process definition: In the process definition, click on the "Add Button" button and select the Button List type. Configure the button list as desired.
Open the process in the frontend: Open the process in the frontend by clicking on the "Open" button.
Observe that the default buttons are missing: Notice that the default buttons in the process definition are missing.
Click on the buttons generated by the Button List: Click on the buttons generated by the Button List to observe that they do not work correctly.
Notice that they do not work correctly, as the system still expects the default buttons to be present: The system still expects the default buttons to be present, which causes the custom buttons to malfunction.
Check the DevTools Console for potential errors or missing button references: Check the DevTools Console for potential errors or missing button references.

To reproduce the error, the following configurations are required:

Process Definition type: Report
Report engine: JR templates
Button List type: Custom

The expected behavior is as follows:

The default buttons in a Report-type Process Definition should not be removed when a Button List is added: The default buttons should remain present in the process definition even after adding a Button List.
Custom buttons from the Button List should work correctly without dependency on the default buttons: The custom buttons generated by the Button List should work correctly without relying on the default buttons.
The system should correctly handle additional buttons without requiring modifications to the default functionality: The system should be able to handle additional buttons without requiring modifications to the default functionality.

The affected version is:

Version number: 24.4.5

To resolve the issue, the following solution design can be implemented:

Modify the process definition to include a separate section for custom buttons.
Update the Button List type to generate custom buttons that do not rely on the default buttons.
Modify the system to handle additional buttons without requiring modifications to the default functionality.

The following test cases can be used to verify the solution:

Given:

A Process Definition of type Report (using JR templates)
A Button List type configured to generate custom buttons

When:

The Button List is added to the process definition
The custom buttons are clicked

Then:

The custom buttons work correctly without dependency on the default buttons
The system correctly handles additional buttons without requiring modifications to the default functionality
ETP-1284 : Button List in Process Definition with JR Report Template Does Not Work - Q&A

In our previous article, we discussed the issue of Button List in Process Definition with JR Report template not working. In this article, we will provide a Q&A section to address some of the frequently asked questions related to this issue.

A: The cause of the issue is that the system expects the default buttons to be present in the process definition, even when a Button List is added. This causes the custom buttons generated by the Button List to malfunction.

A: The default buttons disappear when a Button List is added because the system is not designed to handle both default and custom buttons simultaneously. When a Button List is added, the system replaces the default buttons with the custom buttons generated by the Button List.

A: Yes, it is possible to add custom buttons without removing the default buttons. However, this requires modifications to the process definition and the system to handle additional buttons without relying on the default buttons.

A: To resolve the issue, you can modify the process definition to include a separate section for custom buttons. You can also update the Button List type to generate custom buttons that do not rely on the default buttons. Additionally, you can modify the system to handle additional buttons without requiring modifications to the default functionality.

A: Resolving the issue will allow you to add custom buttons to your process definition without removing the default buttons. This will provide more flexibility and customization options for your process definition.

A: Yes, there are known workarounds for the issue. One workaround is to use a separate section for custom buttons in the process definition. Another workaround is to use a custom Button List type that generates buttons that do not rely on the default buttons.

A: Yes, you can use a different report engine instead of JR templates. However, this may require modifications to the process definition and the system to handle the new report engine.

A: If you are experiencing the issue, you can contact our support team for assistance. We will work with you to resolve the issue and provide you with the necessary support and guidance.

In this article, we provided a Q&A section to address some of the frequently asked questions related to the issue of Button List in Process Definition with JR Report template not working. We hope that this article has provided you with the information and guidance you need to resolve the issue and get the most out of your process definition.