Sarthak Chaudhary

Requirement: The live dashboard refresh buttons are not working and the results do not update. The current workaround involves clearing the browser cache and logging back into JasperServer. This confuses the user and takes additional time for the user. Recommendation: The reason why the data is not updating is because it did not make a request to the database but instead requested it from the Ad Hoc Cache so flushing the cache would work the first time. The real issue here is that the dashboard has auto-refresh set to 2 mins but this didn't refresh the data from the database. To resolve this kindly follow the below steps: 1. Configure the ad hoc cache to flush it once a time limit has been reached: <cache name="adhocCache" timeToIdleSeconds="300" timeToLiveSeconds="600" timeToIdleSeconds: how long a cache item will stay in the cache if it's not used timeToLiveSeconds: maximum lifetime for a cache item, no matter how much it's used Then wait after 5 minutes to see whether the dashboard reflects the newer data with its auto-refresh enabled. 2. In file ..\WEB-INF\applicationContext-datarator.xml, set allowFlushingCacheOnPush to "true" <bean id="allowFlushingCacheOnPush" class="java.lang.Boolean"> <constructor-arg value="false"/> </bean> and restart the JR Server. But the implication here is that every refresh or report execution will be retrieved from the database which can impact db performance. This is not ideal but can be used as a workaround for the time being if it works. We should at least verify whether it works regardless of whether you want to keep the changes

Requirement: Is it possible to translate the input control validation message and report empty message to Swedish, Please see the attached screenshot. Recommendation: The two messages - 'This field is mandatory so you must enter data' and 'You must apply input values before the report can be displayed' are defined in the jasperserver_messages.properties file - so it should be modifiable easily by language with locales as mentioned above or by just changing that particular file. If after this, you see accented letters: The accented characters should be unicode escaped in the properties file. Otherwise, ä = ä and å = Ã¥ So, I believe that is what is happening. If you refer to the guide: https://community.jaspersoft.com/documentation/jasperreports-server/tibco-jasperreports-server-administration-guide/v8/creating-locale/It is stated as follows: The resource bundles described in this document consist of locale-specific Java properties files. Java properties files use the ISO-8859-1 (Latin-1) encoding that is the same as ASCII for all English non-accented characters. For international characters that are not in ISO-8859-1, use Unicode escape sequences (for example u00e9 is é). Therefore in all the translation properties files, you can look up the unicode escape equivalent and use that instead of the accented characters. You can easily look at other property files such as es, and fr to see how they are done. You can google to find the Unicode sequence for the accented characters and use that instead.

Requirement: We are trying to limit the items that appear in the JRS menu by referring to the following site: https://community.tibco.com/s/article/how-limit-non-admin-users-ability-create-or-view If "testArgs="ROLE_SUPERUSER,ROLE_TEST"" is written, the condition will be matched if the user has either "ROLE_SUPERUSER" or "ROLE_TEST". I want to match a user who has "ROLE_SUPERUSER" but not "ROLE_TEST" to a condition. How do I describe the condition that I do not have "ROLE_TEST"? Recommendation: Below would work. For users with "ROLE_TEST", we will not have a view menu option. <!--context for view option on primary menu--> <context name="main_view_mutton" test="checkAuthenticationRoles" testArgs="ROLE_SUPERUSER"> <condition test="!checkAuthenticationRoles" testArgs="ROLE_TEST"> <selectAction labelKey="menu.repository"> <option labelKey="menu.search" action="primaryNavModule.navigationOption" actionArgs="search"/> <option labelKey="menu.all" action="primaryNavModule.navigationOption" actionArgs="browse"/> <option labelKey="menu.favorites" action="primaryNavModule.navigationOption" actionArgs="favorites"/> <option labelKey="menu.jobs" action="primaryNavModule.navigationOption" actionArgs="jobs"/> <!-- <option labelKey="menu.reports" action="primaryNavModule.navigationOption" actionArgs="report"/> <condition test="isCEVersion"> <option labelKey="menu.olap.views" action="primaryNavModule.navigationOption" actionArgs="olap"/> </condition> <condition test="isProVersion"> <condition test="isAvailableProFeature" testArgs="ANA"> <option labelKey="menu.olap.views" action="primaryNavModule.navigationOption" actionArgs="olap"/> </condition> </condition> --> <option labelKey="menu.events" action="primaryNavModule.navigationOption" actionArgs="event"/> </selectAction> </condition> </context>

Requirement: Is it possible to display text in the background of an HTML5 chart in JasperStudio? Recommendation: It is possible to add any text in the background of an HTML5 chart developed in JasperStudio by using the 'Text Field' element from the Basic Elements. Please see the attached screenshot.

Requirement: Is it okay to remove certain log4j-*.jar files? Will that cause the server to crash? Recommendation: Removing these files can cause failures in Ant and issues with generating jar files. It is not recommended to remove them. If there are certain security vulnerabilities related to these JAR files, Jaspersoft will provide a fix for the same.

Requirement: What should be the value for the 'tomcat_installation_type' parameter while installing with the all-in installer when Tomcat already exists? Recommendation: Setting the parameter to existing prevents the Tomcat software from being installed: tomcat_installation_type=existing

Requirement: While using lambda expressions while creating parameter expressions in JasperServer Studio we get the following error: "The target type of this expression must be a functional interface" Recommendation: Given the way report expressions are compiled, you need to explicitly cast the expression to the expected functional type. As in: <parameter name="Parameter1" class="java.util.function.Function"> <defaultValueExpression><![CDATA[(java.util.function.Function<String, String>) ((test) -> {return test + test;})]]></defaultValueExpression> </parameter>

Requirement: Is it possible to enable Font Ligature in JasperServer? Recommendation: 1. Font ligatures are disabled by default in PDF. 2. Ligatures can work when Apache FOP is present on the classpath and the net.sf.jasperreports.export.pdf.classic.fop.glyph.substitution.enabled property is set to true. 3. So it could work on the server if that property is set to true globally or in the report. 4. But it wouldn't work in Studio because FOP is not present there.

Requirement: A report designed in JasperStudio is uploaded to JasperServer. Is it possible to display the name of the input control with more than one line(as seen in the image)? Recommendation: Unfortunately, it is not possible to achieve this requirement. Technically the parameter name can contain a line break, but it the is responsibility of the consuming application (JRS in this case) to format the label properly. A possible solution may be a JRS theme derived from the default one that applies custom CSS on the parameter labels, but still, it will not be able to translate a new line into a <br> but css white-space: pre-wrap; may help.

Problem Statement: Does Jaspersoft support PDF/X-1a when exporting to PDF? Resolution:Unfortunately, PDF/X-1a is not supported by JasperServer. There is no official documentation of the same. However, if this is something that you are interested in seeing the future versions you can log an enhancement request in the ideas portal (https://community.jaspersoft.com/wiki/you-can-log-ideas-jaspersoft-products-jaspersoft-ideas-portal)

Requirement: Is it possible to change the number of days before expiration via configuration for the expiration warning that comes up 15 days before a license is about to expire? Resolution:This value is hardcoded in the JasperServer LicenseManager code. However, this is not exposed due to its sensitive nature. If you still want to change the value you can contact Jaspersoft support who can assist you with the same.

Error Description: While running a studio report that contains a sub-report and a logo in the subreport. When this report is published to JasperServer and run we get an error - 'contextPath needs to be an absolute path' Solution: One possible reason for this error is, that the standard setup is to keep report resources like subreports and images in the JRS repository and not on the server filesystem. So when resources are kept in the FileSystem and not the repository this error is seen. To resolve this, we would need to add the subreport in the repository instead of the file system.

Problem Statement: The requirement is to validate the date minimum value using dynamic value, for now, we use only constant value. Here the Dynamic value is passed through a parameter/Input control by the user. Is this possible to achieve? Solution:On an input-control level, this would not be possible. This is because the min and max values are pre-determined. However, on a report level, you could create a logic for a parameter that validates this date minimum value.