Reporting
ADITO uses JasperReports as its reporting engine for generating structured output such as PDFs, letters, offers, invoices, and protocol documents.
This section focuses on the ADITO-specific part of reporting:
- how report data is prepared in JDito,
- how JasperReports designs are embedded into ADITO,
- how reports are opened in the client, and
- how typical reporting issues are solved in productive projects.
Recommended reading order
If you are new to reporting in ADITO, read these pages in order:
Reporting architecture in ADITO
In a typical setup, reporting is split across three layers:
- A JasperReports design (
*_report) defines the layout, fields, parameters, groups, and optional subreports. - JDito code prepares the data, parameters, and optional subreport datasets.
- A report view or export flow renders the final result in the ADITO client or as a server-side export.
For interactive report views, prefer the Report ViewTemplate together with neon.openContextWithRecipe(...).
neon.openReport() is documented for legacy compatibility, but it is deprecated. New implementations should use report views and the Report ViewTemplate instead.
Topic map
- Jasper Basics: design surface, bands, elements, fields, parameters, and variables
- Create and Open Reports: the standard ADITO workflow from report design to report view
- Advanced Reporting: groups, subreports, nested subreports, and dynamic images
- Font Extensions: make fonts available for exports
- Unicode Support (Special Characters): use Unicode-capable fonts in PDFs
- Troubleshooting: common failures and fixes
- Training Course: Reporting: example-oriented practice chapter
Related references
JasperReports itself is not developed by ADITO. For generic report designer usage, vendor-specific styling options, and detailed Jasper expression behavior, refer to the official JasperReports Library Documentation.