1. Pentaho Reporting – Citrus edition
If life hands you Citrus, make a Report Designer

2. What's on the plate today?
What were we thinking?! Our development goals in a bird's eyes overview
Lots of boxes and arrows: The architecture
Geek's toybox: Let's play with PRD

3. Goal: Changing the game
Number one rule: No more XML
PRD allows to edit all features the XML files can express
Advanced Wizard and Java-API eliminate need to generate XML
A common base: Unified File-Format
One Designer to rule them all*
Predictable, Reliable, Embeddable
Metadata everywhere: Engine-Features, DataSources
Interactivity support built-in
* Terms and conditions apply. Design-Studio will be needed for Bursting or weird hacks that require programming in XML or shooting yourself in the foot. Xactions remain available for those cases. Warning: Using Xactions for simple reports may cause heartburn, short breath, cases of involuntary despair and high blood pressure.

4. Goal: Closing the gap Barcodes, Sparklines, Surveyscale
Side-by-Side-Subreports
Better Datasources in the Engine
Scripting, OLAP4J and Mondrian, Kettle, ..
Built-in parameters
Freeform, Static or Database driven
Dependent parameters
Swing Parameter-UI
Real Rich-Text
HTML (subset) and RTF as input
Next-Generation Wizard

5. Goal: Granny should be able to use it
PRD: Simplified UI
PRD: features always in sync with the engine
Design-Studio no more: Parameter definition made simple
Published report are handled by PRD
Robust chart expressions – less surprises
No surprises: Reports behave the same inside and outside the platform
Swing-Embedding made easy

6. Read my lips: No more Xaction*
Functionality in PRD covers all standard use-cases
With PRD you can
Add parameters
Compute datasets on the fly
Customize reports via PreProcessors
Schedule PRPT files
PRD cannot do
Bursting (yet)
Post-Process the report-result
Anything were the result is not “show me the report”
* Terms and conditions apply. For details, contact

7. Architecture: Pentaho Reporting Process Flow
Report-Definition (MasterReport)
Parameter
Validation
Query/
DataSources
PreProcessor
Report Processing : Data Processing
Layouting, Pagination, Content-Generation

8. Architecture: Reporting in the Platform
WAQR
JFreeReport-
Component
Lightweight
Reporting
Component
PRPT-
Content-Generator
Xaction Engine
Platform Kernel / Core Services
(Security, Audit, Scheduling)

9. Toystory: Let's build an Adhoc-Reporting Solution
Explaining Datasources
Using the wizard
Adding parameters
Adding rich-text comments

10. Toystory: Data-Sources – The building blocks
XML-Support:
Parser/BundleWriter
interface
DataFactory
Reporting Engine
Calls Data-Factories during
Report-processing
Design-Time:
interface
DataSourceEditor
Design-Tools:
PRD/RDW

11. Toystory: Data-Sources in Action
Table data-source
Hardcoded values only
Mainly used for Parameters or Prototypes
Scriptable data-source
Computed data via JavaScript/BeanShell/Python/REX/...
Access third-party systems
Implement complex business-rules
Direct-SQL data-source
Fire (computed) SQL-Queries

12. Toystory: Wizard Wizard-NT evaluates at runtime
Uses pre-configured field and group definitions
Always see's the actual metadata
Get your data your way with flexible templating

13. Toystory: Parameters Parameters are added as first items to a report
Act as static fields in the data row
can influence all parts of a report
Query via attribute-expressions or as query-parameters
Available for Report-PreProcessors
Show up as data in fields
Can be used to control attribute/style-expressions
Parameters are typed, type must match
Default-Validator can check values against datasets

14. Toystory: Rich-Text Text-Elements can interpret content as rich-text
Disabled by default for compatibility and performance reasons
Controlled by an attribute
Uses Swing-Documents
subset of HTML 3.2 (+ subset of CSS)
RTF files
Or any other styled-document*
* supplied as javax.swing.text.Document