In rare cases, when saving older reports with SQL Expression Fields, the fields were incorrectly saved, making them invalid.
In rare cases, older reports had issues with SQL Expression Fields which led to them being loaded in the latest version of i-net Clear Reports as having the name “null”. This caused the report to no longer work.
Prompt names including “</script>” in the name could cause issues in the HTML-based Prompt Dialog. The names are now correctly escaped.
An IllegalArgumentException occurred if a continuous chart was drawn with multiple null values.
A login request (HTTP code 401) need a long time with JBoss because the wrong content length was send to the client.
Report Reader:
In some cases when reading a Crystal Reports template, lines were read as being below the boxes, however this is not possible in Crystal Reports. Now, the boxes are always placed below any line elements in the section, according to how Crystal Reports works.
When reading Crystal Reports templates, summary fields with a “reset on group” setting were incorrectly read as resetting on the field the group was based on rather than on the group itself.
The group option “evaluate on change of field” was incorrectly read from Crystal Reports templates by the Report Reader.
When reading a report using the Report Reader on systems with Crystal Reports 2008 SP3 or higher, an API change introduced in the SP3 update caused the error “Object reference not set to an instance of an object” for certain summary fields.
The 'case sensitivity' parameter was ignored, if the formula function InStr was executed on database.
A section was as blank (empty) detected, if it contains only a JavaBean on top of this section (Top = 0).
Fixed a security bug which allowed a user to be partly authenticated in the system when another user opened the remote designer.
Formulas could not store any and all characters, even ones normally invalid in XML documents.
Special fields with numbers (such as Page Number and others) lost any custom number format settings when the report was saved and re-loaded.
The XML RPC method “listResources” returned an error if any of the resource names used multi-byte characters.
Special field “Page N of M” was not displayed correctly in PDF export, if the font SansSerif was used.
Field references in the field browser tree were incorrectly counted when they were referenced by parameter default value formulas and then undoing multiple steps of report design.
PDF export:
HTML export: The first paragraph was not shown, if it was empty.
Text interpretation “HTML(Advanced)” now relies on the actual fonts used by any renderer(e.g. PDF or XLS) which provides a more accurate render output for fonts not known to the Java font system.
Shutting down then restarting an i-net Clear Reports server caused the logging to be deactivated the second time around.
The data of the report was emtpy if the report was executed three times by using of report data cache.
Non JDBC Database classes has not worked, if the data source configuration of the report does not exists on the server. In this case it has tried to connect to a JDBC connection.
