i-net Clear Reports

i-net Crystal-Clear runtime

New Features / Improvements

  • It is now possible to create PDF files according to the PDF/A-1b standard using a property in the PDF export dialog of the Java viewer or by the using new URL parameter “pdfa”.
  • Remote Interface: User “System Administrator” added. A login into the Remote-Interface without an administrated Login-URL will grant all rights to this user, called “System Administrator”.
  • URL parameter “colswidth” added. It specifies the column widths (fixed width) for CSV export.
  • Excel export:
    • 1-byte characters can now be used as thousand separator. If 2-byte characters used, only the low byte will be shown.
    • The values of date and time will be converted to the client time zone, if the option 'useClientTimezone' has been set.
  • New report url parameter “filename” to specify the target filename of the exported report.
  • The method Engine.getRecordCount() now returns the record count for subreports, also.
  • The formula statement 'option loop' and the basic variable type 'double' are fully supported now.
  • Chart:
    • The behavior of continuous date line and area chart was changed. The line goes to the zero in the gaps between two values. This involves the series with following summary operations: sum, count, distinct count.
    • The grouping weekly in a continuous date chart uses sunday as first day of week, like the data grouping in the report.

Fixed Bugs

  • TrueType fonts which were incorrectly initialized were displayed with a height of 0.
  • Property “Print At Bottom of Page” did not work correctly for areas. Each section of an area was displayed at the bottom of a separate page.
  • There was a rarely occurring problem that old reports with summary fields were not able to be read.
  • Endless loop occurred if Underlay Following Section was enabled for a large section.
  • StackOverflowError occurred if nested if-then-else statements used in formulas.
  • There was a problem reading a Crystal Reports template with ReportReader, the message was “Object reference not set to an instance of an object”.
  • Exception “Invalid render state” occurred if a “new page after” section was encountered before a section had been displayed.
  • Lines and boxes that are continued on the next page, started under the page header. Now, they start under the repeated group header.
  • Lines with “Move to Bottom of Section when Printing” enabled were not displayed on the next page if the section spanned multiple pages.
  • Element borders were drawn into adjacent sections if the element was on the edge of the section.
  • The multi-column layout of a report was incorrect if it was used together with the section property “Underlay Following Sections”.
  • The set line width of boxes was used for positioning the boxes even when line style was set to NO_LINE.
  • Formulas:
    • The population standard deviation summary function now returns an empty value until a valid value has been read.
    • Because of a bug it was not possible to use string range promts in formulas.
    • Problems with user-defined functions occurred if Java primitive types were used as method parameters.
    • The formula function 'isnull' was executable on the database if it's parameter was a boolean field.
    • It was not possible to overwrite a variable, that was created with StoreNumberVar in the main report, with StoreNumberVar in the subreport.
  • Excel Export:
    • Cross-Tabs were incorrectly displayed when exporting the report to Excel format. The first column was not exported.
    • Thousand separator not displayed if procent format was used.
    • The position of the '%' -symbol has not been set, if the log level was lesser than WARNING.
  • Security issue: Using a modified report URL, it was possible to download files from the i-net Crystal-Clear web context, if the file crystal.war was unpacked.
  • Report Reader: Mailing label and multi column reports were not read properly by the .NET-based Report Reader.
  • A subreport in the page footer was not displayed if the first subreport section was higher than the subreport itself.
  • Error with database column of type CHAR occurred if it contains empty strings.
  • If muliple directories has been specified in “Font Path” property and occurred an error during reading fonts from one directory, then the other directory was not read.
  • Names of embedded fonts in the font path has been searched only case sensitive.
  • NullPointerException occurred if user defined string collation for grouping and sorting was used with an empty locale.
  • IllegalDatePeriodException occurred if time field was used as column or row in a crosstab.
  • Changing the alias of a table source led to problems when the report had an SQLField as an element in the report.
  • An endless loop in the scheduler occurred with large scheduler jobs, if hard disk cache or database cache was used.
  • ReportReader: The formatting of field parts in text labels was not correctly read from Crystal Reports templates.
  • Text export:
    • Some lines in cross-tabs were missing.
    • Because of the shadow of lines blank rows occurred in a crosstab.
  • Data export:
    • It has occurred that columns of the exported csv file contains records of multiple database fields or special fields, e.g. Page Number.
  • Set and reset reference of a summary field by group with TopN was faulty.
  • Error in SQL statement: Comma between tables in the From clause was missing, if a stored procedure and more than one table has been joined.
  • PDF export:
    • Subreports containing images, were sometimes not included in the created PDF file.
    • If the property 'Replace Missing Characters' was enabled, then subreports were sometimes not included in the created PDF file.
    • Unicode characters, containing some special byte values(0x28,0x29,0x5c), could not be displayed correctly in the bookmarks of the PDF file.
  • Sometimes cache was hanging for 15 minutes after refresh button in Java report viewer was clicked, if embedded fonts were used.
  • N-datatypes of JDBC 4 (e.g. NClob) not supported, if Java 6 was used.
  • Translations in the report was not used for parameter fields (prompts) and formulas.
  • Scheduler: It was not possible to use embedded fonts with the print action of the scheduler.
  • For elements using simple HTML interpretation, justified bullet lists were not justified in the first line.
  • A rare bug that caused an extra empty line in text fields including field parts and empty lines was fixed.
  • RTF export: Not transparent images were not displayed, if the RTF files was opened in editors, like: OpenOffice writer.
  • A vertical line or box from the page header to group footer section was not drawn on a page, if it was the group footer of the last record, the group footer was on the top of the next page and there was no group footer on the current page.
  • The methods RDC.loadEngine(File file) and RDC.loadEngine(File file, xxx) could not read report templates that was saved as directory.
  • Excel Export:
    • If the first group is invisible and the group header in the second group is suppressed and the group footer in the second group contains some data, the new sheets pro first group have not been created.
    • Text strings was formatted with STANDARD-Format instead of TEXT-Format. Therefore numbers and dates, that are written as text, was shown in Open Office with an apostrophe as first character.
    • No columns were added to the .xls file for thin field or text elements (width < 3mm).
  • The height of a section was increased to the default crosstab height, if the section contains a very small crosstab (smaller than the crosstab default height) and if the height of the section was smaller than the default crosstab height.
  • Because of a bug in the Java VM on the Mac OS, a security exception occurred if a not privileged user tries to use user preferences and i-net Crystal-Clear internally tries to use the System preferences.
  • ArrayIndexOutOfBoundsException in the translator occurred if the same placeholder, e.g. {0}, was used multiple times within the same string.
  • Fields in the subreport were not displayed, if the property “Suppress if Duplicated” was activated and the text interpretation “Html (advanced)” was used.
  • The text property “Manual Formatting” was not working correctly in many cases, if it was used for crosstab fields.
  • ArrayIndexOutOfBoundsException occurred during the execution of a report that was designed with i-net Crystal-Clear version 10.
  • Infinite loop occurred, if “Suppress if Blank” was enabled for a section that contains an empty subreport with enabled “Suppress report if no rows”.
  • ArrayIndexOutOfBoundsException in RTF export occurred.
  • The toWords function has used the server locale instead of the default locale. Therefore toWords with an English output was not possible on a server with Chinese locale.
  • It was not possible to change the default font style Bold of field elements in a crosstab to another style, e.g. Standard. After reopening the rpt file, the style was again set to Bold.
  • OutOfMemoryError occurred, if Remote Interface or Repository Browser were used heavily.
  • Security fix to prevent cross-site scripting (XSS).
  • In some cases a performance issue has occurred on Linux servers.
  • PDF Export:
    • Error “OTF type is not set!” has occurred during PDF export, if non-embeddable fonts were used.
    • Sometimes file handles for embedded fonts were not closed. Therefore the exception “too many open files” could occur.
    • It could occur that characters of east european fonts were not displaed, if non-embeddable fonts were used.
    • With enabled area keep together in some cases the Java viewer has shown the page before after a click on a group tree node.
  • StackOverFlow/infinite loop on auto-generated summary fields has occurred.
  • Problem with Apache Derby DB during connection creation occurred.
  • In the excel export a slash as delimiter in a custom date format was displayed using the locale default delimiter. Now, a slash is used independent of the locale.
  • In rare cases a NullPointerException occurred during font initialization, if statistic data was empty.
  • IllegalArgumentException occurred: The name of a sum field cannot be empty.
  • Invalid license key exception occurred sometimes if BouncyCastle JCE provider was used.

i-net Crystal-Clear - Java Viewer

New Features / Improvements

  • Method showPrompts() added to ViewerContext, enabling you to customize prompting behavior of the viewer by providing your own ViewerContext.
  • Help button added to the export dialog.

Fixed Bugs

  • Parameter Fields dialog
    • Date time ranges only went to midnight in the AM of the end date instead of up until midnight of the day following the end date.
    • Various issues were fixed for the date range prompt dialog, including date ranges not being stored correctly for later prompts.
    • The prompt dialog had graphical issues on systems with text sizes turned to a larger DPI for accessibility.
    • Time prompts did not accept time entries unless the exact second was entered as well. A time prompt will now accept a simple “10:12 am” as well.
    • When reloading a prompt dialog with a prompt accepting multiple values, the descriptions of the values would disappear.
    • Using 120 DPI under Windows 7 could lead to a graphics issue with the prompt dialog.
  • Used in a record selection formula, a date range prompt only went until midnight in the AM of the ending date. This means any date times during the ending day of the range were viewed as outside of, rather than inside the range.
  • File extension of the default file name in the export dialog was missing if the file name or report title contains 2 dots.
  • A deadlock has occurred sometimes, if reports was printed in the background using SwingReportView in the EventThread.
  • Formular Printing: Although the property “Enable Formular Printing” was enabled, it was not possible to print in the non-printable area with some printers.
  • Print dialog ignores PrintService in PrinterJob if SwingReportView.showPrintDialog(Component, PrinterJob, HashPrintRequestAttributeSet) was called.
  • The width of the margins on the printout did not match the designed margins, if the default paper size of the printer was Letter and the designed paper size was A4 and vice versa and you changed the paper size in the print dialog to the designed paper size.
  • Endless loop occurred because of java.util.WeakHashMap, which a non-thread safe object.
  • Attribut “Permissions” was missing in the manifest file of ReportViewer.jar. This is required since Java 7 update 45.

i-net DesignerXML

New Features / Improvements

  • In the case a deadlock occurs, the designer will now offer a help page at startup for contacting support for further help.
  • It is now possible to set a different grid distance for the x and y coordinates in the Design view - i.e. using a rectangular grid rather than a square one.
  • New unit “grid points” added. It allows to place report elements according to grid point distances.
  • Formula Editor: Function “CurrentDrillDownLevel” has been replaced with “DrillDownGroupLevel”. At runtime “CurrentDrillDownLevel” is supported for downward compatibility.
  • Paragraph attributes are also displayed in design view.
  • Menu items undo / redo added to the popup menu of text elements.
  • Methods DesignerDataModel.getAvailableFontsFromRepository() and DesignerDataModel.createViewer() added.
  • It is now possible to set the “first line indent” value for each individual paragraph in a text label.

Fixed Bugs

  • Drag and Drop was not possible in text elements.
  • SQLField optimized: The database used to be contacted when loading a report into the designer if there were any SQLFields. Now it will only be contacted at design time if an SQLField has an unknown value type.
  • NullPointerException occurred sometimes while closing the i-net DesignerXML application.
  • Memory leak occurred during editing of text fields.
  • Loading a report from the repository, making a change, and then saving the report again without looking at its preview caused the report's stored thumbnail to disappear.
  • Visual Database Wizard:
    • Adding a data source to a report which contained SQL fields was incorrectly not allowed.
    • The default SQL statement created for converting a report to SQL from within the Visual Database Wizard was not correct if the report contained a Stored Procedure as a table source.
  • Parameter Field Properties:
    • Various usability issues and bugs regarding date and datetime formatting have been fixed.
  • Canceling an attempted database connection caused an error to be displayed even though the connection was closed correctly.
  • SQL Expression Editor:
    • Adding an SQL expression field to a report which contained a data source still needing a valid password was not possible - now, the password is requested instead.
  • Formula Editor:
    • The formula function “DefaultAttribute” has not worked on any property. If the property does not support a user defined default, now the function returns null instead of an error.
  • Translator:
    • The translations in subreports were not stored in the rpt file.
    • It was not possible to translate subreports on demand using translator.
    • At execution time, the translations were not used for parameter fields and strings in formulas.
    • It was sometimes not possible to translate strings in a subreport using the translator.
    • It was not possible to use the same placeholder, e.g. {0}, multiple times within the same string.
  • Copy and paste from/to programs with HTML clipboard format did not work.
  • Default format for fields did not work, if the fields has been embedded into text fields.
  • If a property formula could not be parsed, the property dialog was not displayed.
  • A selected report element was removed from the report, if the delete key was pressed to delete a field in the field browser, e.g. a parameter field.
  • The property “Possible undo steps” was removed from the Designer Options dialog, category “Editing”.
  • The property “Manual Formatting” in the “Property Editor”, category “Text”, was always disabled.
  • Report as Folder:
    • If a report containing images was saved as folder, then it was not possible to reopen it, after the folder was added to the subversion control system.
    • If a report was saved as folder, the complete folder structure was overridden and not just the folder's content. Therefore the source control's .svn subfolders were removed completely.
  • NullPointerException occurred after the refresh button in the Visual Database Wizard was clicked.

Repository

New Features / Improvements

  • Repository locations can now be enabled and disabled or administrated in the configiration manager.

Fixed Bugs

  • Reports loaded from a remote repository were not correctly rendered anew each time in the Designer but rather would sometimes return cached results.

Configuration Manager

New Features / Improvements

  • System Permissions: Guest account added.
  • Data Source Configuration import: there were XML encoding issues when importing files with XML entities.
  • It is possible to use private certificates for the login URL.

Fixed Bugs

  • Data Source Configuration export: Encoding issue with umlauts and other special characters occurred.
  • The help frame for the remote datasource configuration web tool had incorrect formatting and was difficult to read.
  • Using Opera 9 in a non-English locale, some of the remote interface's help pages and labels were mixed English and foreign language. This was due to an Opera 9 bug, and a workaround was found.
  • It was not possible to import a properties file containing the key “allow.param.dll” as a configuration.

 

© Copyright 1996 - 2017, i-net software; All Rights Reserved.