Security issue “Cross-Site Scripting” occurred
Unknown operation: com.inet.report.renderer.doc.controller.bk@0
occurred with TotalPageCount
(NofM) in subreports
Property RELOAD_ON_NEW_REQUEST
does not work if there was no output format specified in the report URL
“java.io.NotSerializableException: com.inet.font.truetype.i” occurred if a font path was set and “Page NofM” or PageCount was used in very large reports. Because of that the server could hang
Regression occurred: Special field “current user” and the formula WebUserName returns the display name. Now it returns again the id of the user and not the display name
Embedded fonts used in PDF documents embedded in a sub report where missing in the created report
Layout of text in right to left fonts (Arabic, Hebrew) was wrong, if the text parts have different styles (bold, italic, etc.). It occurs in the output formats: PDF, PostScript, image and Java report viewer
Sorting in charts with 2 groups was incorrect if the first category value does not contains all series values of the chart. In this case the sorting of the series was incorrect
PDF export: Embedded fonts with glyphs in the range of 0xF000-0xF0FF were not dispalyed in PDF file
CSV export: Empty CSV export with encoding UTF8 opened with MS Excel. MS Excel shows the content “” in the first cell instead of a complete empty table
ORA-01000: maximum open cursors exceeded - occurred if Oracle JDBC driver was used
NullPointerException in debug mode if a plugin has no version information
Patching the SQL command to query the metadata (column names) was wrong if the command contains function listagg(…) within group …
. In this case WHERE 1=0
was added to the listagg function
XLSX / ODS export: Percentage number was incorrectly displayed (multipled by 100)
Patches the SQL command to query the metadata (column names) was wrong if the SQL statement contains strings which contains brackets, e.g. REPLACE(A.FIELD,';)',')')
. In this case WHERE 1=0
was added after the ORDER By
clause
Break algorithm improved for Text Interpretation “HTML(advanced)” to prevent breaks in text lines
Oracle table source identifier with a package name will be always used as name of a stored procedure and never as name of a table. This makes it possible to use the same name for a package stored procedure and a table
IllegalStateException: REGISTER error occurred because a classloader loop occurred if the i-net Clear Reports libaries has been added to /lib directory