This section describes currently known issues in this release of JasperReports Server:
| • | JRL-242 (was 17824): While Fusion Charts support annotations, JasperReports Server and Jaspersoft Studio don't support them. We may address this issue in a subsequent release. |
| • | JRS-15530: The UI Samples page for administrators, available in previous releases, has been removed. When testing themes and other cosmetic changes or customizations to the web UI, please navigate to a page with the component you're changing rather than viewing the samples page. We may address this issue in a subsequent release.
|
| • | JS-19100 (was 30018): When an XML/A provider returns data to the Ad Hoc Editor, JasperReports Server sometimes must convert the datatype to string. For example, an XML/A provider may return data of type currency; in an Ad Hoc view, such currency data is a string that displays as a symbol (such as $) and a number. When such an XML/A-based Ad Hoc view is saved as a report, its datatypes are converted again. JasperReports Server attempts to convert the data to their original types, but in some cases, such as currency, no such type is available, and so currency data is converted to type double. In reports created from an Ad Hoc view, XML/A data that was returned with datatype currency is displayed as a number; the currency symbol is omitted. Wei may address this issue in a subsequent release. |
| • | JS-30677 (was 43514): We have found that earlier versions of PhantomJS may not support or include all the fonts JasperReports Server uses when exporting dashboards. For example: |
| • | If a dashboard contains fonts for certain locales (such as Japan and China), the text isn't rendered properly in the exported dashboard. |
| • | If a table in a dashboard has been filtered or sorted, the sort and filter icons aren't rendered properly in the exported dashboard. Sorted crosstabs exhibit similar behavior. |
If you experience such issues, upgrade PhantomJS to at least version 2.0.
| • | JS-30847 (was 43707): If a dashboard contains an image dashlet that relies on the repo: syntax to refer to its image, and superuser exports the dashboard (using the repository's Export context menu item or the Manage > Server Settings > Export page), the image isn't exported with the dashboard. We may address this issue in a subsequent release. |
| • | JS-31493 (was 44499): The dual-measure tree map, tree map, and parent tree map chart types don't currently support the hyperlink functionality when an Ad Hoc view or report is used in a dashboard. We may address this issue in a subsequent release. |
| • | JS-34346: This release changes resource visibility constraints in multi-tenant deployments (that is, those that include more than one organization). The change disables certain cases of improper resource referencing, such as providing an absolute repository path (starting with the root organization) for a resource referenced in a report. If you have a reference to an image, a subreport, or other resource that has an absolute path (or uses a $P{} parameter that later resolves to an absolute path), the server returns an error. Please update such references to use path that are visible to users in the organization in question. Consider using relative paths, or use the public folder for reports used by multiple organizations. |
Recommended Comments
There are no comments to display.