Release Notes V1.0.RC5
Concealed parameters input
In Eclipse parameters definition, "do not echo" property is now taken in consideration for String and Integer types.
By setting this property to one of your parameter, it will be displayed as a kind of password in parameters dialog:
"All values" item
When we define a combobox report parameter as "not required" in Eclipse designer, the reportlet Engine automatically adds "All values" item in last position.
In previous versions, the value returned by this item is the BIRT "default value". This behavior may be annoying and intrusive. From final v1.0, by default it is unchanged, but we can now define a custom property to override this.
For example, the "interactive-table" demo report has been updated like this:
- "Country" parameter has now a BIRTdefault value "USA" and a custom property "_allvalues" set to "all"
- "Year" parameter has now a BIRT default value "2010" and a custom property "_allvalues" set to -1
- The other parameters are unchanged, so their "All values" item still use their respective BIRT default value
Both "all" and "-1" values are processed by the dataset query so that they return all rows, see this article for more informations.
Interactive Organization chart
A stunning HTML5 Organization chart
Special characters in a drillthrough action
- In v1.0RC4 and previous versions, using special characters (é, î, à, ß, etc..) in a drillthrough action may cause problems. Most of the time you will never encounter this issue, because well-designed reports use alphanumeric IDs for parameters values. However sometimes we don't have any other choice but using a "label" as a report parameter value, for example when we use a flat file or a web service as datasource. This is fixed in final V1.0
- Problems specific to Interner Explorer have been resolved. You should not have anymore 'UTF8 encoding' issues in final V1.0 version
JBoss 7 special characters in images URL
With Visioneo reportlet, BIRT images URL include the portlet session ID in their query String. Depending on your application server and its configuration, this ID may contain some special non alphanumeric characters. If this character has a specific meaning in a query string (such "&", "=",...) the image won't be found when the report is rendered in HTML format. Currently, "+" character has been reported for JBoss7 in this thread. This is the only character from JBoss' default alphabet involved with the issue, and it only affects JBoss7+
Normally, using these characters in sessions ID shouldn't cause any trouble because they are encoded, but the same bug mentioned above related to drillthrough actions comes into the scene. It is fixed in final v1.0. As a workaround in v1.0RC4, on jBoss7 you may want to modify the alphabet used to generate sessionsID, replacing "+" by any ASCII character which is not interpreted in a query string, and valid in a file path. For example, '.','-','~' and '_' are fine.
Special characters in report parameters prompt/helptext
The Visioneo reportet displays report parameters prompt and helpText defined in Eclipse designer. When they contain some special characters such quotes, we may encounter display issues. Fixed in final v1.0: characters are now escaped in report parameters prompt/helptext.
In some circumstances RC4 version fails to start with JBoss 5&6. Fixed with final version. However there are specific install steps, see this technote.
- In v1.0RC4, two CSS lines have a global scope and may have a side effect on your portal components / custom portlets and on BIRT reports styles, they are removed in final V1.0
- In some circunstances, the Visioneo merged css file is inserted upto three times in a page. Fixed in final version.
- Many UI display issues are fixed, especially related to the report parameters.
jQuery UI 1.10.2
Upgraded to the latest stable jQuery UI 1.10.2
- Great enhancements in the dialog handling
- Many display issues fixed (spinner, combobox, accordion widget,..)
- Combobox with filter
Visioneo reportlet is now compiled with EhCache v2.6.3. This allows to take advantage of the most advanced features, and for very large contexts an easier upgrade to BigMemory GO.
Hide toolbar option
- The toolbar may be annoying when we navigate within a report. "Hide toolbar" option has been improved: the toolbar is now definitively hidden, unless the page is refreshed or if we click at the very top-left corner of the portlet window.
- A new portlet preference is defined to control if it must be hidden by default, when a portal page has just been loaded. The treemap demo now makes use of this feature, the toolbar is hidden until we click at the top-left corner.
- Detection of mousenter/mouseout events sometimes failed with HTML5 canvas objects, it has been improved.
- Hide toolbar effect sometimes caused a small display bug, it has been simplified
The reportlet now offers facilities to invoke toolbar dialogs from an external custom portlet
uPortal & Apache Pluto
A jsp page issue prevents v1.0RC4 from working correctly with uPortal and Pluto portlet container. Fixed in final version
Successfully tested on the latest portal Gatein / exoPlatform v3.6
SQL Injection blacklist
The default list of characters / expressions blacklisted to protect your data against potential SQL injection attack is a little bit more permissive. In particular "@" character is now authorized by default, to be able to use emails as report parameters. This character is used as stored procedure prefix with some databases, but for most contexts it shouldn't be a security hole. Anyway you can still control this blacklist from "patternBlacklist" parameter in portlet.xml.
In v1.0RC4 and previous versions, "displayText" parameter property is not correctly localized: it makes use of the default language of user's web browser, when it should use the language selected in the portal. Fixed in final v1.0.
Many BIRT report developers don't know this feature exists, though the "displayText" property is very useful: it allows to insert within reports your parameters labels. For example, if we create a report parameter named "Measure" to select which measure should be used, we can invoke in BIRT scripts/expressions:
In the new demo report "Regions tree" we have a "Title" parameter and a "Measure" parameter, among others. The final report title is built with this BIRT expression:
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
Integration tests v1.1.1 16 March 2013
Release Notes V1.0.1.Final 15 March 2013
Release notes v2.1 852949 Views
Release notes 0.9.1 271053 Views
Release notes 0.9.2 261098 Views
Release notes 0.9.3 259755 Views
Release Notes v1.0RC3 259453 Views
Release Notes v1.0RC4 244665 Views
Release notes 0.9.4 243657 Views
Release notes v1.2.2 216945 Views
Release notes v2.0 204770 Views
Release notes v1.3.0 174423 Views