Eclipse is probably best known as a Java IDE, but it is more: it is an IDE framework, a tools framework, an open source project, a community, an eco-system, and a foundation.https://www.eclipse.org/eclipse.org-common/themes/solstice/public/images/logo/eclipse-200x200.png
In conjunction with the Callisto release, the BIRT team is pleased to announce the availability of BIRT 2.1. The features in this release expand on the already impressive features of BIRT 2.0 and offer improvements in many areas such as context-sensitive help, Charting, Data Set creation, parameterization, Library creation and Template development. Below is a description of some of the key features that are now available.
The complete list of features for the final 2.1 release is available here.
BIRT 2.1 introduces many charting improvements. Some of the more notable include a new Bar Stick subtype for Stock Charts, legend auto wrapping, improved interactivity and scripting, marker lines, enhanced axis scaling, legend text rotation, additional y axis support, added data point markers, and percentage pie charts. Rendering of Pie, Area and 3D charts has also been improved and a new PDF Device renderer is available to the charting engine.
The BIRT 2.1 Chart Builder features accessibility support, sticky dialogs and online help.
BIRT provides a Hyperlink Editor, for the creation of links to other BIRT reports, external content, and bookmarks within the same report. This editor has been improved to support features such as hyper linking to a report table of contents entry, discovering of required parameters and drilling to a report document. These features can speed the development of reports intended for drill through applications. For example if a detail report is created and that report is then grouped, another report can use the Hyperlink Editor to link to the TOC of the detail report. This operation requires the developer to specify the target report and select the target TOC radial within the Hyperlink Editor. No additional work is required.
Specifying a report document as the target for a hyperlink can be useful in cases where the detail report is quite large or the data changes infrequently. When the master report link is selected the detail report will not re-execute, but will use the report data that was retrieved during the last run of the detail report.
When deploying data centric applications to the Web tier it is often desirable to share pooled data base connections for performance and resource management reasons. BIRT 2.1 has expanded on the capabilities of the JDBC Data Source, by adding the option to specify a JNDI Name to look up a data source name service for retrieving a pooled connection.
The JNDI URL property can also be modified using BIRT property binding. This would allow changing the JNDI URL based on parameters, session attributes or other script values, at runtime. The enhanced JDBC Data Source also supports using a jndi.properties file for configuring the initial context environment. By default this file will be read from the drivers directory within the JDBC plug-in.
Some reports need to alternate page layout properties, such as orientation, within a given design. BIRT 2.1 now offers support for this feature, by adding a master page property for report elements. The report designer has been enhanced to allow multiple master pages within the design. When a page break occurs before an element, this property is checked and if needed the master page is changed. Data Binding within the master pages is now possible as well.
Data filtering and report customization is often achieved with parameters. How parameters are presented and collected is usually of paramount importance to the application developer.
BIRT currently has a very flexible parameter collection model, where the report designer can define very simple or complex parameters. One of the more sophisticated methodologies is to use is cascaded parameters. With this approach, a group of parameters are defined in such a way that the each parameter choice affects the next parameter within the group. This usually means the available selection list is reduced or changed for the subsequent parameter based on the prior parameter selection. For example, if a report is written that is presenting geographic sales data, a user of this report may only want a particular region for a given country. This can be achieved by creating a cascaded parameter group containing two parameters, country and region. When presented to the end user, the country selection list would display all countries. After selecting the desired country, the second parameter list for region would then be repopulated with only the regions for the desired country.
In prior versions of BIRT, the above example required that a developer add a Data Set that queried the Data Source for country and region within one operation. This is no longer the case. Cascaded parameters now support multiple Data Sets. This allows the report designer to define at each subsequent level of the cascade an entirely new query, possibly even from a different Data Source. The nested query can then use the prior parameters within its query to cull the result set.
Illustrated below is an example of a cascaded parameter that presents products by lines. This cascade has two parameters. This first is “ProductLines”, which queries the Data Source for all product lines. The second is “Product”, which queries the Data Source for products and is culled based on the product line selection.
Data Sets are one of the fundamental BIRT elements for retrieving data. Data Sets contain tabular data, fetched from Data Sources, which can be used within the BIRT data container elements such as Tables and List. These BIRT elements are only bound to one Data Set. If the report developer wishes to display data from multiple Data Sources within a given Table this becomes complex. To address this issue, BIRT 2.1 now provides the ability to create a special Joined Data Set. The Joined Data Set allows combining of two existing Data Sets using Inner and Outer Joins. The new Joined Data Set also supports filtering and computed columns.
After the Joined Data Set is created, it functions as any other Data Set in the design. This feature is especially useful when combining data from multiple Data Sources. For example, incorporating financial data from one Data Source with HR data from an entirely different Data Source. Joined Data Sets can also be further joined with additional Data Sets.
BIRT 2.1 supplies language packs for easy translation. Currently twenty-two languages are available.
All of the BIRT offerings have been improved in the area of accessibility. These include proper HTML formatting, shortcut keys, keyboard access to most functions and proper tagging of images and charts.
BIRT 2.1 features a new Binding Editor, which allows more control over how data is bound to a container element, such as a Table. BIRT data container elements are no longer bound directly to a Data Set but are now bound to an intermediate layer. This intermediate layer can comprise data from a Data Set as well as computed columns. This design approach makes a much clearer delineation between BIRT Tables and Data Sets and offers clearer scooping while using the Expression Builder.
If a report is structured to display Orders, Order Details, and Products as nested Tables, in that order, linking these tables using just the Expression Builder can be tedious. Pictured below is the Binding Editor for the Order Details in the example above. The Status column of the Orders table is made available to this Table using the Binding Editor.
Using the Expression Builder it is now clear what data is available to the selected container. In the example below, a column has been added to the Products Table using the Binding Editor. The Expression Builder shows that this column has access to three Tables: Products, OrderDetails, and Orders. This reflects that the Tables are nested.
Within the Group Editor it is now possible to set page breaks before and after a group. For every group change a new page can be added. This feature supports suppressing the first and last page break. An option has also been included in BIRT 2.1 to allow the group header to be repeated when the page change occurs.
Many additional features and improvements have been made in BIRT 2.1.
In the area of Data Sets and Data Sources, connection profiles are supported, Scripted Data Sets can now use parameters, Data Set Parameters can set Report Parameters as default values, and the Designer caches the Data Set metadata to allow disconnected report design.
A resource path is referenced for libraries and images, which aids in deploying reports to different environments.
The BIRT 2.1 Viewer provides a control for Printing of reports.