Pentaho Reporting

Pentaho Reporting encompasses more than two dozen software projects that facilitate creating and publishing data-driven business reports.

Enterprise Edition documentation

Enterprise Edition customers have access to the following professionally written, tested, and actively maintained Pentaho Reporting documentation in XHTML format through the new Pentaho Knowledge Base, or in PDF format through the Help menus of the appropriate software:

• Pentaho User Console 2.0 Enterprise Edition Guide
• Pentaho Enterprise Edition 2.0 Administrator's Guide
• Pentaho Report Designer 2.0 User Guide

In addition to these comprehensive guides, there are also support articles and tech tips available through the Knowledge Base.

For Pentaho Community Edition users, this Wiki and the Pentaho Forum are the two best resources for Pentaho Reporting documentation and support. The below-listed articles were contributed by Pentaho employees and open source community members.

Contributing community documentation

All registered users are able and encouraged to directly fix any errors and eliminate any omissions in this Wiki. Feel free to contribute information or instructions for any topic relating to the Pentaho Report Designer, ad hoc reporting, the Pentaho Reporting engine, Metadata Editor, or Design Studio. However, unless it's specifically a sub-topic of an existing article, please create all new pages relating to Pentaho Reporting as children of one of the below topical pages, and all articles pertaining to Metadata Editor and Design Studio as children of those sub-pages.

Community documentation for the Classic-Engine Design-Tools

• Report Designer
• Report Design Wizard

Pentaho Reporting Classic Engine (JFreeReport 0.8)

The Pentaho Reporting Classic Engine is the proven and stable branch of our embedded reporting engine. It is a banded reporting engine that is based on an absolute layout.  Our plan is to evolve this engine into 'Pentaho Reporting 1.0'.

Developer Guides

• Classic Engine How-To Docs
• Dependency documentation
• Developer's Getting Started Guide
• Pentaho Reporting's Modular Design
• Using the DocumentBundle Reader and Writer
• Parameter Definitions
• Report Processing State Diagramm
• Code-style Definitions
• Functions And Expressions

Installation Guides

• Report configurations and the boot process
• Use of TrueType Fonts
• Define Selectable Report Encoding

User Guides

• Classic Engine Algorithm
• Advanced Reporting Guide
• Pentaho Reporting XML Definition formats
• Layout Restrictions for Table-based and Plain-Text output
• Report XML Definition DTD/XSD
• Style-Keys Reference

• Shortcut: Formula Syntax

Pentaho Reporting Flow Engine (JFreeReport 0.9)

The Pentaho Reporting Flow Engine is the next generation reporting engine for the Pentaho Project. As we are still adding features to the engine to get a complete first version of this thing, this is the right time to collect ideas and feature-requests to make the Engine the best Reporting Engine on this planet.This part of the Wiki itself is subdivided into three sections. The Flow-Engine will evolve into 'Pentaho Reporting 2.0'.

• A short guide to the style-resolving process
   

Archived JFreeReport Documentation

The documentation section acts as general library. It contains the content for the manual and all how-to's and technical articles that have been or will be written. Before posting an feature request, peek in here to see whether your requested feature isn't already implemented.

• JFreeReport 0.9 documentation
• JFreeReport 0.9 How-To Docs
• Documentation To-Dos

To-Do List

The To-Do list contains all tasks, that have been already scheduled for a later (or possibly the next) release.

Feature Requests

Please enter these requests into our JIRA system.  The Wish-List contains all (and I mean it: all) ideas, features and usage scenarios that could be possibly done using JFreeReport. Except for doing the Dishes or Time-Traveling, any idea is welcome here.

Once the idea has been developed enough, it will move on the To-Do list.

If the idea is already implemented, it moves into the documentation section - either as Documentation-ToDo or as link to the manual.

If the idea is rejected (for instance if it is not solvable, or is not even remotely related to reporting or content processing), it ends up in the [Recycle Bin].