i-net Crystal-Clear

Changes in Release 7.6.04

i-net Crystal-Clear runtime

New Features / Improvements

  • NEW: Dynamic Prompts: It is now possible to set dynamic default values which are fetched at run-time. This is possible either by providing a database field or by providing an SQL query which fetches the records.
  • NEW: Java Beans as data source: Java Beans can be used as data sources for i-net Crystal-Clear reports. This means the data can be provided by an application inside an application server and simple JavaBeans can be used as data sources for i-net Crystal-Clear at design-time and runtime.
  • It is now possible to specify null when setting an allowed value range for prompt fields. This enables the possibility of open intervals.
  • The JFreeChart library was renamed to jfreechartCC.jar to separate this from the original library.
  • TXT export: Line spacing properties are now supported.
  • PDF export: Bookmarks are now written in Unicode.
  • Excel export: 3 Properties added:
    • “celltruncate”: if true, then strings which are too long for their cell will be truncated
    • 'firstgroupassheets': if true, then a new sheet will be created for every instance of the top-most group.
    • grouplevel: specifies the number of group levels which are to be visible in the Excel outline.

Fixed Bugs

  • PS export:
    • Invalid Postscript files were produced if specific images were included in the report and “Total Page Number” or “Page N of M” was used in report.
    • JavaBeans with images were sometimes rendered incorrectly in Postscript export.
  • PDF export: Rotation for fields with Text Interpretation “HTML (advanced)” was not correctly calculated.
  • Data (CSV) export:
    • The order of the fields in the created .csv file now corresponds to their x-coordinate or y-coordinate (if x-coordinates are equal) in the detail section. In previous versions the fields were added to the csv file in the order in which they were added to the report template.
    • WrongMimeType exception could occur when data export was used.
  • RTF export: The first line of text could be incorrectly positioned depending on the value of the line space property.
  • Setting a line spacing factor did not replace the absolute line spacing setting, and vice versa.
  • Formulas:
    • Some keywords of Basic syntax were viewed as keywords for Crystal syntax and therefore caused problems if used as variable names (e.g. “let” or “dim”).
    • Statement blocks in individual cases in select..case statements in formulas were not parsed correctly.
    • Variable references, which can be shown by pressing F2 while highlighting a variable name in the formula editor, were not displayed correctly for newly created formulas.
  • An IndexOutOfBoundsException sometimes occurred if the description section (upper left corner) of cross-tabs contained elements.
  • For certain field elements, the “justified” alignment was not observed.
  • Refresh did not work if an implementation of the PropertiesChecker modified the key on the server side.
  • Page Break Bug: The Page Header / Footer sometimes displayed information from the previous or next page, e.g. if “New Page After” or “New Page Before” was used together with a suppressed section.
  • Text Interpretation - RTF:
    • If the default value for code page is declared but not defined in the rich text, a NullPointerException occurred.
      Now the RTF Parser will set the default to cp1252.
  • The PromptField API was improved greatly by the addition of the class DefaultValue, which holds both a value and a description. All methods in PromptField for adding and removing default values have been deprecated and are to be replaced by the corresponding methods using DefaultValue. Additionally, it is now possible to set a DynamicValueProvider instead which provides default values at run-time.
  • Regression in 7.6: Fields were overwritten if “Underlay Following Sections” was enabled and the following section was suppressed (fixed in 7.6.02).
  • Decimal places of large BigDecimal numbers (more than 15 digits) truncated if custom number format was used.

API Changes

  • Added Methods:
    • PromptField.setMinRangeValue(Object)
    • PromptField.setMaxRangeValue(Object)
    • PromptField.setDefaultValueProvider(DynamicValueProvider)
    • PromptField.getDefaultValueProvider()
    • PromptField.getDefaultValues()
    • PromptField.setDefaultValues(DefaultValue[])
    • PromptField.createDefaultValueFromFormula(String, String, Engine)
    • PromptField.createDefaultValueFromFormula(String, String, int, Engine)
    • PromptField.addDefaultValue(DefaultValue)
    • PromptField.setDefaultValue(int, DefaultValue)
    • PromptField.getDefaultValue()
  • Added Classes:
    • com.inet.report.DatabaseBean
    • com.inet.report.DefaultValue
    • com.inet.report.DynamicValueProvider
    • com.inet.report.FieldValueProvider
    • com.inet.report.QueryValueProvider
    • com.inet.report.SQLValueProvider
    • com.inet.report.database.beans.BeanDataSourceManager
    • com.inet.report.database.beans.TransferServletException

i-net Crystal-Clear - Java Viewer

New Features / Improvements

  • Export without preview but with export dialog: A new method export(Component, RenderData) was added to the ViewerContext interface which allows for exporting without having to have a ReportViewer created. Only a RenderData object needs to be passed for it to work.

Fixed Bugs

  • Parameter Fields:
    • It was possible to close the prompt dialog with one of the prompts having a value which was not allowed. This then caused an error after the dialog was closed. Any problem is now shown before the dialog is closed.
    • There was an unclear error message when a string prompt was either not long enough or too long for the set value range.
    • With prompts which were not used in the report, it was possible for an internal error to stop the report from being rendered.
    • Currency prompts are now handled the same as numbers in the prompt dialog, to avoid confusion regarding the exact currency being used.
    • When providing an HTML formatted prompt description, there were formatting problems in the viewer prompt dialog.
    • It was not possible to enter an empty string for string prompts with a value range, even if the value range had “0” as its minimum length.
    • It was possible to set default values which were forbidden by a set value range. This led to problems especially when prompts were set for “default values only”. Now, all default values must be legal in order to be set.
    • The error message when entering values outside of the allowed value ranges was improved for date, datetime, and time prompts.
    • It was possible to set a negative value for a string prompt's limit value range.
  • The zoom levels while zooming out and in were sometimes irregular.
  • It was possible to use the viewer's snap shot tool to copy from outside the viewer area.
  • The group tree space was too wide if there were long group names.
    Now the group tree's width starts off as no more than roughly a third of the viewer's width.
  • Umlauts and other special characters, entered in the URL as a URL encoded parameter were decoded incorrectly by the viewer.
  • ReportView.extractNavigationView did not work as documented: the navigation view did not disappear.
  • The “export without preview” sample now exports the report without rendering it additionally to the requested format in the Java Viewer format.
  • RTF export: Labels with a width of 0 but with a border were not shown correctly.
  • HTML export: It was not possible to create a file with the ending ”” with the Export dialog, only ”.htm”.
  • SVG export: The export dialog displayed ”.svg” file but an ”.htm” file was produced.
    The first file of the SVG export is an HTML file. Therefore the extension was changed to ”.svg.htm”.
  • Regression in 7.6: Status of the export was not written into the status bar (fixed in 7.6.02).
  • List of export formats in the export dialog was sometimes too small (fixed in 7.6.04).
  • The viewer requested the same report page with old data (vgen = 0), also if data was changed and ReloadOnNewRequest was true in the configuration of the server (fixed in 7.6.04).

API Changes

  • Added Methods:
    • ViewerContext.export(Component, RenderData) - export without preview but with an export dialog

i-net DesignerXML

New Features / Improvements

  • New: Java Beans can now be added as data sources.
  • The Designer Prompt Dialog has been re-designed for greater user comfort. The default values can now be entered via a simple table with editable cells. Also, it is now possible to set “dynamic prompts”, i.e. prompts whose default values are generated at run-time. Advanced prompt options were moved out of the first panel into an “Advanced options” panel.

Fixed Bugs

  • The report templates for the report wizard were optimized for being able to create a sub report using the report wizard.
  • The help entry for the “Change Position” dialog was missing.
  • The report browser displayed the content of the sub report instead of the content of the main report sometimes.
  • Regression: Designer embedded does not start (fixed in 7.6.02).

i-net Crystal-Clear Setup

New Features / Improvements

  • A log-file (Install_V7.6_xxx.log) in the installation path contains all messages and errors that occurred during the installation.

Fixed Bugs

  • The uninstaller of an installation created via console failed with a NullPointerException.
  • The setup script created on Windows can be used on other platforms as well. Only the path entries have to be modified for the platform on which it will be executed.
  • NullPointerException occurred during installation of component: “Apache PHP Servlet” (fixed in v. 7.6.01).
Documentation Sitemap

i-net software strives to provide accurate product documentation. Please give us your feedback using the form below.
NOTE: This form is for documentation feedback only. For technical assistance, please send an email to crystalclear@inetsoftware.de.

 

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