- Crosstab Improvements
- Multi-View Items
- BIRT Chart Improvements
- Bidirectional (Bidi) Support
- Scripting Improvements
- Improved External Style Sheet Support
- Horizontal Page Break Support
- Library Changes
- Multi ResultSet Stored Procedure Support
- Project Specific Settings
- Connection Profile Wizard
- SQL Query Builder Prototype
- Copy and Paste Formatting
- Preview Extension Point
In conjunction with the Ganymede release, the BIRT team is pleased to announce the availability of BIRT 2.3. The features in this release expand on the already impressive features of BIRT 2.2 and offer improvements in many areas such as Query Building, Charting, Usability, Cross Tables and Emitters. Below is a description of some of the key features that are now available.
To review project details for the 2.3 release, see the project plan pages, which are available here.
This debug configuration allows the debugger to run within the current instance of Eclipse and supports Java and Java Script events. The currently loaded BIRT engine can be used to process the report, or a separate instance can be specified using the Engine home setting. In addition, the specific engine task can be specified to match the deployed environment. The task type setting supports the RunAndRender, Run, and Render tasks provided by the BIRT engine. The task type can also be set to perform a Run task followed by a Render task. By using the Classpath tab, specific Java event handler projects can be added to the classpath to support debugging Java event handlers.
The debug configuration can be launched through the Debug perspective, or by selecting the run menu item within the Report Design perspective.
In addition to validation of scripts, the error descriptions within BIRT have been improved to better diagnose problems.
Displaying data in a cross tabulated format offers many advantages for data interpretation and analysis, and is often a requirement for information delivery applications. BIRT offers dynamic cross table and data cube elements to meet this requirement. The data cube element appears in the Data Explorer view and allows the developer to build cubes based on existing data sets. These cubes are constructed using dimensions and measures. The dynamic cross table element can be placed on the report canvas and bound to a cube. The dynamic cross table permits specification of dimensions for the columns and rows while measures are defined at the intersection point. BIRT 2.3 provides many enhanced features for the cross table element. For example, report elements can now be placed in the cross table header.
Filters, which cull the data displayed in the cross table, can now be applied to measures. In prior releases of BIRT filters could only be applied to the dimensions.
In this example, the amount measure is filtered to only show values over 50,000, which results in the following cross table output.
Cross tables can now be set to display empty rows and columns. In addition, the text to display in an empty cell can also be configured.
Measures represent the intersection point for the column and row values and are by default displayed as an alphanumeric value. New for BIRT 2.3 is the ability to display these values graphically.
When showing the data graphically, the chart used to represent the measure can be configured using the BIRT chart wizard. For example, the following shows the amount measure presented as a tube chart.
Individual charts can be displayed for each measure and can be generated against the vertical or horizontal dimension. Charts can also be used for cells containing total elements.
Cross tab elements now support derived measures. These can be created by using the Derived Measure dialog, which is launched with the menu context item “Add Derived Measure”. The BIRT Expression builder is used to construct these derived measures and all cross tab bound items are available for use within the expression.
BIRT currently binds data to report items such as charts, tables, and cross tables. Data can be retrieved from BIRT datasets or another report item. This feature has been further refined with this release to allow report items to have multiple views, wherein all views share the same data, filtering, and grouping. The view of the data determines how it is to be displayed and is essentially just another report item sharing the same graphical space and bound data. Currently only tables and cross tables support this feature and the secondary view must be a chart.
The chart view can be created by right clicking on the table or cross table report element and selecting the “Create Chart View” menu item.
This will launch the Chart Wizard. After the chart is created, the view displayed of the data can be selected using the view tab at the bottom of the report element.
The Charting package continues to be a highlight for BIRT and with this release many improvements have been made. Some of the improvements are explained in the sections above, which describe multi-view report item support for tables and cross tables. In addition, grouping and sorting for charts has been improved. In previous releases of BIRT, categories and optional Y series grouping were available, but sorting these groups could not be done with a separate data value. With this release of BIRT, a sort on field has been added to both the category and optional Y series grouping dialogs. Many new grouping unit types are also available, including quarters for date time fields. The interval for numeric data types can now be set to a decimal value.
Charts, embedded in reports, can now consume data from report cubes. This is in addition to the existing support for BIRT data sets and report items.
Charts created from cubes can also be filtered based on the values selected for value and category series as well as the optional Y series grouping.
With BIRT 2.3 it is now possible to set the start angle of the first slice in a pie chart. This can be done by using the Pie Rotation slider in the Format Chart tab of the Chart Editor wizard.
Additional chart examples have also been added the Chart Examples view. Other chart improvements include ellipsis support for long axis labels.
As a rule, directionality of a whole document or its piece is made consistent with the language it is written in. For instance, predominantly Arabic or Hebrew content should be oriented from right to left (RTL), while that written in English or German - from left to right (LTR).
To address this requirement, BIRT 2.3 delivers a new feature - customizable content direction.
Direction of the entire report or a particular element can be expressed by "bidiLayoutOrientation" and/or "bidiTextDirection" properties respectively. These properties are not yet exposed in the GUI layer. To apply them when creating a report in the Designer, use the XML Source editor view.
For example to set the direction for an entire report add the “bidiLayoutOrientation” setting to the top level report properties. Valid values are rtl or ltr.
To set the direction for a given element, add the “bidiTextDirection” setting to the properties for the specific report element.
This feature is extended to all currently supported formats. Illustrated below is an example in PDF format.
Direction can be also manipulated programmatically using the Design Engine API, for example:
DesignConfig dconfig = new DesignConfig(); dconfig.setBIRTHome("/birt/engine"); Platform.startup( dconfig ); IDesignEngineFactory factory = (IDesignEngineFactory) Platform.createFactoryObject( IDesignEngineFactory.EXTENSION_DESIGN_ENGINE_FACTORY ); IDesignEngine engine = factory.createDesignEngine( dconfig ); SessionHandle session = engine.newSessionHandle( ULocale.ENGLISH ) ; ReportDesignHandle designHandle = session.createDesign(); designHandle.setProperty("bidiLayoutOrientation", "rtl"); ............ LabelHandle labelHandle = designHandle.getElementFactory( ).newLabel( null ); labelHandle.setProperty("bidiTextDirection", "ltr"); designHandle.getBody( ).add( label ); ............
In addition to the new events for the cross tab element, chart scripting has been improved to support beforeDrawMarker and afterDrawMarker events. Using these events the individual markers for the chart and legend can be altered. For example, the following screenshot illustrates script that hides legend entry graphics and changes the size, type, and color of the chart markers based on the chart data.
BIRT currently supports styling of report elements, by either creating a new style that is stored in the report, importing an existing style sheet, which is also stored in the report, or by linking to an external style sheet. In prior versions of BIRT, if using a linked style sheet, the css file had to be located in the resource folder for the given project. With the 2.3 release, BIRT provides the ability to link the style sheet at view time, and it can be referenced as a full or relative URL.
This feature creates a link tag that references the style sheet in the emitted html, and supplies the proper class names for all styled content.
When developing reports that contain tables or cross tables that contain many columns, page width may become a problem. This is especially true, if the report needs to be printed or the developer wants to prevent excessive scrolling. To address these issues BIRT 2.3 now supports a horizontal page break setting for tables and crosstabs. To use this feature, within a table select the column(s) you wish a page break to occur and navigate to the Page Break field in the Properties View. Then select “Always” either for the “Before” or “After” setting. This setting will instruct the report engine to insert a page break at that column. To configure this setting for a crosstab element, select the crosstab and navigate to the Column Area tab, then select the Page Break field and add the appropriate page break setting. Illustrated below is an example of setting the horizontal page break for a table.
The Library Explorer View has been renamed to Resource Explorer and supports multiple enhancements, including navigating all resources within the specific resource folder. These include images, scripts, jars and libraries that located in the resource folder. Many UI changes have also been made to the Resource Explorer view to facilitate better resource management. These changes include the ability to add or create new content within the resource folder using an improved context menu. In addition, adding content to libraries has been improved with BIRT 2.3 to support publishing any report element to a library by using the context menu.
BIRT currently supports calling stored procedures through the JDBC driver. BIRT 2.3 offers an improvement to the data set editor that now allows the developer to specify a result set number or name when calling stored procedures that return more than one resultset. Oracle stored procedures that have output parameters that are reference cursors are supported as well.
BIRT uses properties defined in the preferences pages to configure how reports are generated and displayed. For example, a resource folder setting is used to locate report libraries. In previous versions of BIRT these settings where treated as global settings for the entire workspace. Many of these settings can now be configured specifically for a given project. This will allow multiple projects in the same workspace to configure separate specific settings. These settings include chart data preview rows, crosstab settings, element names, resource and template folder locations. Presented below is an example of setting the resource location for a specific BIRT report project.
When creating a data source in BIRT, the developer has the option to use a connection profile to retrieve data source properties. This connection profile can be created with the Data Tools Platform project’s (DTP) Data Source Explorer view and contains the needed information, such as username and password, to connect to the data source. In order to use this feature, in earlier versions of BIRT, the connection profile needed to be created prior to designing the report. In this release of BIRT, a new wizard is available that allows these connection profiles to be created within the data source editor.
BIRT 2.3 delivers a prototype feature that adopts the DTP SQL Query Builder tool (SQB) and use of the DTP Database connectivity framework. The integrated SQB provides both a textual editor and a graphical builder for users to build a SQL query. User edits made in either the textual or graphical pane are automatically reflected in the other. It is enabled by a built-in SQL parser, with knowledge of the database catalog found in a connected JDBC data source. See Bugzilla entry 204344 for the known limitations in this version. This new ODA data source is an early adoption of the SQB feature in DTP. In order to get early feedback on its usability and functionalities, this feature is introduced as a prototype, and does not claim any backward compatibility support.
To use this feature when creating a data source, select the “create from a connection profile in the profile store” radial in the New Data Source wizard. Using the connection profile wizards create a new profile or select the pre-defined connection profile named "BIRT Classic Models Sample Database". Using the sample database profile is shown below.
Once the data source is created, create a new data set and the Query Builder Prototype should be available in the Data Set Type drop-down control.
BIRT supports linking and importing style sheets that can be applied to report elements. This allows a set of reports to share common formatting. BIRT 2.3 adds the ability to copy the formatting specified for a report element to another report element.
BIRT currently uses an application context object to store engine configuration information, such as image locations, URL configurations when generating hyperlinks, and setting image formats for chart generation. This application context object is available throughout the generation and rendering phases of the reporting pipeline. This object can be manipulated in the Report Engine API and with the use of session variables, before executing a report. This can be beneficial for storing your custom objects in the application context, which can then be retrieved using BIRT expressions or scripting. Testing reports that use this feature within the designer can be somewhat difficult, as your custom objects are usually not available at design time. To address this issue, BIRT now provides a preview extension point. This extension point allows the developer to create a plug-in that can modify the application context within the designer, before a report is executed.
This extension point provides two methods. The getName method is used to name your implementation and the getAppContext method is used to retrieve the application context object from your plug-in. In the following example we implement a preview extension point to add a test string to the application context.
Once the plug-in is created and deployed to your designer, you can enable it in the preferences.
The test string can now be referenced in BIRT expressions and scripting within the designer by entering testStr.
This release contains many other features, including support for parameter retrieval while using a Java scripted data set, support for the includeScripts property in libraries, and support for computed measures.
In addition to these some other features of note include:
Back to the top