Birt reports compatibility
The current distribution .war file integrates the 4.2 birt report engine. The next releases will embed the latest birt versions as soon as they are available.
Servlet request functions
This is the major cause of issues. Some reports embed scripts which use the
reportContext.getHttpServletRequest() object. For instance, to get the current remote user within a report:
If it is used with the visioneo reportlet, this function returns null and will probably make your report fail. Beyond the fact visioneo uses a portlet request and not a servlet request, a report should not have to deal with this kind of issue, and guess itself in which context it runs.
There are several ways to get the remote user in the visioneo reportlet, for instance:
and for the principal user:
Some reports use the request session to store / retrieve informations, with something like:
This won't work with the reportlet, because it is using a portlet request, not a servlet request. The portlet request can be accessed in a BIRT report context like this:
However you should use it with cautions, because the cache engine does not take session attributes in consideration. If you need to exploit user attributes in your reports with Visioneo, please refer to this article.
<visioneo reportlet root>/birt/resource
Please refer to the knowledge base article "How to add report & sub-folders" to get more informations about resources.
Visioneo embeds a powerful persistent cache which can be shared across users. More informations available in the knowledge base article "Document & rendering cache".
This feature is not yet implemented, it is scheduled for further releases. Though a report should still run even if this parameter type is used, the parameter dialog will replace the cascading widget by a simple text input.
If you encounter an issue with one of your reports by using the reportlet, the first thing to do is to check if it works or not with the Eclipse Birt WebViewer.
If it works with the WebViewer, and you can't pinpoint the precise cause with the log messages (the birt engine logs and the visioneo logs), the safest way to make it fix is to reproduce the bug on the birt sample database "Classic cars", or provide a sample data file. You can then post your report .rptdesign on the forum, or send it at:
Repository portlet for BIRT 21 October 2016
Birt required / facultative parameters 11 April 2016
Document & rendering caches 08 February 2016
How to define reports access permissions 06 November 2015
How to define a portal repository 28 October 2015
Inter-portlet communication 26 October 2015
Server-side Autocomplete 14 October 2015
How to disable the load fragment window 08 October 2015
How to automatically adjust charts size 10 September 2015
How to hide parameters labels 07 April 2015
How to add reports & subfolders 303598 Views
How to build your own theme 288423 Views
How to modify reportlet styles 287084 Views
Inter-portlet communication 276436 Views
Document & rendering caches 273396 Views
Birt required / facultative parameters 263028 Views
Report data volume 262504 Views
Ajax inter-portlet communication 259021 Views
Reports datasources: Stored Procedure vs SQL query 247252 Views
How to automatically adjust charts size 232607 Views