To align with Broadcom's best practices for managing system resources, particularly when dealing with large or complex reports, we need to prevent users from directly running reports in Jaspersoft.
Currently, users have two direct execution options for immediate report execution by right-clicking on a report in the repository:
Accidental direct runs are common, especially on macOS, where the "control + right-click" menu can be triggered unintentionally. These direct runs can negatively impact system performance by consuming significant resources, which is a key reason for encouraging scheduled report execution.
We are looking for a solution to disable these direct run options, leaving only the "Run in background" (scheduled) option available. Is there a configuration setting in Jaspersoft to achieve this, or is a UI-level customization, such as modifying HTML/CSS, required to hide these options?
Here are two approaches to prevent direct report execution in Clarity Advanced reporting (Jaspersoft)
Option 1: Enabling reports to be run from Classic PPM > Reports and Jobs
This is the recommended method for controlling user access to reports and ensuring all executions are managed through the JasperSoft scheduler API.
To enable a custom report to be run from Clarity's "Reports and Jobs" menu, you must:
Option 2: UI Customization (Workaround)
This option involves modifying a configuration file to remove the menu options from the Jaspersoft UI. Note: This is a UI-level workaround and may be reverted during system upgrades.
There is no built-in configuration setting to remove the "Run" and "Run in New Tab" menu options. However, you can manually edit the actionModel-search.xml file to hide them.
Locate the file: Navigate to jaspersoft_tomcat_home\Webappseportservice\WEB_INF\actionModel-search.xml.
Edit the file: Remove the following two <condition> tags from the file:
<condition test="checkMode" testArgs="browse,search,library">
<simpleAction labelKey="RM_BUTTON_RUN" action="invokeRedirectAction" actionArgs="RunResourceAction"
clientTest="canBeRun" className="up"/>
</condition>
<condition test="checkMode" testArgs="browse,search,library">
<simpleAction labelKey="RM_BUTTON_RUN_IN_NEW_TAB" action="invokeRedirectAction" actionArgs="RunResourceInNewTabAction"
clientTest="canBeRun" className="up"/>
</condition>
Save and restart: Save the modified file and restart the Jaspersoft services for the changes to take effect.