Knowledge Base (Display) Knowledge Base (Display)

Release Notes V1.0RC.4

For this version, in addition to bug fixes, most of the effort has been concentrated in the WSRP 2.0 support (See OASIS for more informations about it) , portal user attributes, Google maps integration, and parameters enhancement. Additionnally a few other great features have been implemented, read these release notes for more details!

 Web Service Remote Portlet (WSRP 2.0) Supported!

 

  An incredible feature! Visioneo reportlet will be the only reporting solution allowing this with its full GUI: the application can be used as a "proxy" on multiple remote portals, exactly like if it was installed locally on each portal. Potential benefits, more informations and a demo will be soonly available. 

A WSRP service is enabled on visioneo.org, so that you can set up a "consumer' in your own portal to test it.  See this article for more informations

As a consequence, the reportlet is now set up by default as "remoteable" in Gatein,  Liferay and JBoss EPP configuration files. It is a problem for Liferay 5 which does not support this. Liferay 5 admins will have to modify "liferay-portlet.xml" to remove "remoteable" and use the Liferay 5 DTD. More informations in the "Liferay install" knowledge base article.

Render & BIRT Documents location

It is now possible to specify an absolute path for /document and /render folders, in your portlet.xml descriptor. It is probably a good practice to set up these working folders out of the scope of your application server, to make clusters more efficient. For a large context, in order to optimize performances, you should put them on a fast drive:  RAM Disk,  SSD disk, SAS bay etc.

BIRT Engine 4.2.1

The reportlet 1.0RC4 is compiled with a v4.2.1 BIRT engine. Unlike previous releases, visioneo reportlet is now distributed in two versions:

  • "Quick start", a package containing the reportlet  application and all dependencies in a single .war file. It is the same kind of package used for previous releases, very easy to install.
  • A "light" bundle: some dependencies, in particular the BIRT engine, can be downloaded and installed as a separate package. It is important to note the Birt engine code is not modified in any way, so you can definitely get it from Eclipse site instead.

This light bundle is a little bit more difficult to install, but much more flexible. You may want to install a birt engine as a shared library on your application server, because it makes possible to restart the reportlet application independantly in a few seconds, without problems which may be caused by a birt platform restart. Reloading your reportlet application is necessary when you want to apply modifications from configuration / JSP files (portlet.xml, localization files, styles CSS, web.xml, ehcache, JSP pages, etc.).

jQuery framework

Visioneo reportlet 1.0RC4 now ships with the latest jQuery UI 1.9.2, and jQuery core 1.8.3. 

qTip2 is not used anymore, and has been removed. This tooltip plugin is awesome, but for maintainability considerations the new tooltip embedded in jQuery UI is used instead.

Portal attributes integration

A significant work has been realized to enhance the integration of portal attributes in BIRT reports with visioneo,  in particular the ability to set user attributes as security filters in a report dataset query. A demo report is uploaded, demonstrating how to use a Liferay custom user property (for example, a business office) as a security filter. By the way several issues have been highlighted with the cache engine and the report context, they are all fixed in 1.0RC4.

complete article  for reports developers in the knowledge base


To avoid headaches when developing your reports, all exposed attributes are now displayed in the reportlet admin mode, at the bottom of  "Security" tab:

Drillthrough dialog improved

  • The toolbar is now embedded in the dialog's title (top left corner), see the live demo
  • 'Done' button has been removed, to give more place to the report content. This dialog can still be closed with the icon at the top right corner, or with "escape" key.
  • 'Export' option is now available for drillthroughs
  • Many annoying drillthrough bugs are fixed

Datepicker display format

In previous versions, the jQuery datepicker always displays 'Date' parameters in a technical format 'yyyy-mm-dd'. In v1.0RC4, a more friendly localized format is used. For example in french and english (en_GB), date values are displayed with 'dd/mm/yyyy' format, when in en_US it is 'mm/dd/yyyy'. You can test this behaviour with the Portal attributes demo , a US icon has been added in the language portlet. It is possible to customize this format for every language.

 

Note the Date validator has been rewritten to use this localized date format. For example, if the current user has selected english US language:

 

In previous versions, a constant min/max value was defined for all date widgets: 

min = current date - 12 years

max= current date + 1 year

It is now possible to setup a min/max value from a birt report design (custom properties), relatively to the current date.

Ergonomic autocomplete multiselect

To meet the requirements of some projects, this widget has been dramatically enhanced: selected items are now individually displayed below the autocomplete field, therefore it is not possible to mistake anymore when entering data. Additionnally, users can dynamically reorder their selection with a simple drag&drop. Unlike all other multiselect widgets, this selection order is kept the same when it is sent to BIRT reports! With the powerful BIRT scripting abilities, it is then possible to take advantage of this selection order within reports. For example we can use a scripted dataset based on the autocomplete parameter to create a "sort key" column.

A new demo report is available here!

 

By the way, note the "accordion" feature applied to BIRT parameter groups has been improved, now it fills all the space of a dialog window.

Preferences mode when Birt report design is wrong

In previous versions it is not possible to switch to preferences mode when the report stored in portlet preferences has design errors. Fixed in v1.0RC4

 

Client-side cache disabled

The server-side cache from Terracotta is so fast and efficient, that a client-side cache may be an unnecessary source of confusion. A new init parameter allows to enable/disable this local cache, by default it is now disabled. In portlet.xml:

<init-param> <name>useClientSideCache</name> <value>false</value> </init-param>

 

Google maps

A framework  has been developed to add easily BIRT dataset records in a Google map, and embed this map in your report.

  • Display a rich and fully customizable infoWindow for each marker (may include a chart, table, drillthrough hyperlinks...)
  • Drill to a detailed report
  • Apply color coding and different size on markers , depending on conditions in your dataset
  • Flexible legend allowing to toggle markers
  • Customize images used for markers
  • Latitude and Longitude can be retrieved from a BIRT dataset, or geocoded on the fly (see Google maps terms of service for geocoding)
  • Support several maps in a same report
  • Support several maps in different reportlet windows on a same page!

Google maps demo report (.rptdesign), documentation and support will require to buy a support ticket.

It is designed to work both with the visioneo reportlet, and Eclipse BIRT designer / WebViewer as well, so you can use it even if you don't plan to deploy the reportlet in your context.

See this very nice example in the live demo:

A similar framework based on OpenStreetMaps should be implemented as well!

Spinner widget

 A new "spinner" widget is applied on your BIRT report parameters, when they are defined as a number type (Integer, Decimal or Float). It is possible to control  min, max, step or page options in Eclipse Designer, from your parameters user properties!

Key up / down,  Page up / down and mouse Wheel are supported to update values. Open the dialog parameter of the "Google maps" demo report to see this new feature in action!

Alternative display styles are available: simple (just an empty input field), number (takes advantage of the native html5 input number). See parameters of  the "Welcome" report to review these different styles. You can easily customize "number.jsp" to add new styles, or modify predefined ones:

Birt engine tmp folder

In previous versions you may noticed the Birt engine can create tons of temporary files in your java temp folder. From RC4 release, these files are smartly stored in a visioneo subfolder java.io.tmpdir/visioneo/birtengine:. The "caches" folder is the default location of your terracotta caches, you can change it in ehcache.xml file.

java.io.tmpdir

visioneo

birtengine

caches

from vRC4, a periodic scheduled java task clears the content of this birtengine folder automatically.

Demo reports

  • The "welcome report" had errors due to the themes of the visioneo common BIRT library,  fixed in this RC4 version. It might be important if you plan to use these themes  your own reports.
  • A new beautiful "Sparklines" report has been added in the Eclipse folder.
  • A new report demonstrates how to take advantage of the auto-complete widget

RptDesignHandle errors in log

You might see in your logs errors such:
SEVERE: Failed to open rptdesignhandle for report xxxxxxxx: null
It occurs when a report does not have a valid thumbnail defined within its "rptdesign" file. There isn't any consequence, except logging this error. It is fixed in v1.0RC4

PDF Exports extension

PDF exports are created with extensions .pdf-1, .pdf-2, .pdf-3 depending on the option selected. Fixed in v1.0RC4, they all have a simple .pdf extension.
 
Tags: release notes
Average (0 Votes)
Most Recent
Release notes v3.2 24 November 2015
Release notes v3.1 26 September 2015
Release notes v2.2 19 August 2015
Release notes v1.4.1 06 December 2013
Release notes v1.4.0 03 December 2013
Release notes v1.3.0 13 October 2013
Release notes v2.0 26 September 2013
Release notes v2.1 01 August 2013