Running dashboard via visualize.js has date filter displaying incorrect date format after modifying date.format in jasperserver_config.properties

Issue:

We have modified the below configuration files to change the default date format and restarted the TIBCO JasperReports® Server :

..WEB-INFbundlesjasperserver_config.properties:

from:

date.format=yyyy-MM-dd

to

date.format= dd-MM-yyyy

..WEB-INFbundlesadhoc_masks.properties:

added:

ADH_100_MASK_date_3 = dd-MM-yyyy

After logging into the TIBCO JasperReports® Server, we ran a dashboard containing an Ad Hoc view with a date filter in a dashlet. 

The date format from the date filter correctly displays dates in the format of dd-MM-yyyy.

However, after running the same dashboard using visualize.js, the date format from the date filter incorrectly displays dates in the default format of yyyy-MM-dd.

Solution:

This is a known defect that has been fixed in the following cumulative hotfix:

hotfix_JRSPro8.0.2_cumulative_20220609_1155.zip

The specific defect incident is:

JS-65763 [case #2099441,+1] Non Standard US Date format is not working with date field in JRS 7.9 cascading IC

To resolve this issue, download the above mentioned hotfix (or a later hotfix) from: 

https://support.tibco.com/s/hotfixes

and follow the instructions documented in the readme.txt (located under 'jasperserver-pro' sub-directory).

It is important to follow the additional instructions at the end of the readme.txt file pertaining to this specific defect:

Details for JS-65763 fix: The fix introduces ability for Input Controls to use configurable
`date.format`, `time.format` and `datetime.format` formats declared in the `jasperserver_config.properties` file.

To enable feature:
1. Open `js.spring.properties` file
2. Comment out `bean.calendarFormatProvider=isoCalendarFormatProvider` line
3. And uncomment `bean.calendarFormatProvider=messagesCalendarFormatProvider` line

Note: The defect was reported in TIBCO JasperReports® Server 7.9.0 and hence this issue should also be observed in 7.9.x which has it's own corresponding hotfix.