The platform provides a flexible mechanism to create report plugins that will naturally fit into existinginterface, thus system integrator only need to concentrate on the business functionality around generating specific report.
Report API provides several interfaces for the report plugin:
- ReportDescriptor - which defines the report unique ID and parameters that is requires/allows
- ReportWorker - which allows to provide options for "select" style parameters and generates the the data for the report
- ReportGenerator - which converts data object created by ReportWorker into a report file
By default most of the reports would be configured for the Admin app to provide business users with various statistical and accounting data. All out of the box report definitions are specified in Spring context file manager-report.xml. For customisations it is advisable to create your own maven module that would have core-module-reports as a dependency and would specify adm-servlet-ext.xml toin the application.
Namely reportDescriptors list and reportWorkers map would need to be extended in order to include Spring beans of your custom reports.
In terms of storefront (i.e. customer facing application), you can generate ReportDescriptor object programmatically and trigger report generator with specific data in order to generate report file. We will see how this can be accomplished by looking at the delivery report example.
Delivery report, learn by example
Delivery report represents a PDF invoice that can be generated for any given order. We will look into the particulars of the report configuration, which should give an idea of how the whole report framework works both in Admin app and the storefront.
Custom implementation 3.6.0
As mentioned in the extension point section report Spring beans are defined in the manager-report.xml. Specifically if we examine how delivery report (with id reportDelivery) is configured we see the following bean definitions.
ReportDescriptor bean which is part of the reportDescriptors list
The descriptor defines reportId (unique ID for this report plugin), xslfoBase (PDF report specific layout file) and one mandatory parameter orderNumber.
DeliveryReportWorker bean which is part of the reportWorkers map
And AdminReportGeneratorImpl bean which is the default implementation of the report generator which is backed by XSLFO to generate PDF files.
Thus with this configuration what will happen is that:
- Business user opens Reports section in Admin app
- ReportService will generate list of all available reports using getReportDescriptors() that will populate the selector
- Business user chooses specific report and clicks add tab
- ReportService will run the getParameterValues() that will populate all available selection values
- Business user clicks run button to generate the report
- ReportService triggers generateReport() with selected parameter values that uses report worker to generate the data object and passes it to the report generator to generate report file. Specifically AdminReportGeneratorImpl will serialize data object into XML and then load the XSLFO template (i.e. client/order/delivery.xslfo), then generate the PDF using the Apache FOP library.
- Business user can use the file download facility to download the generated file
Reports via extension 3.7.0+
Reports framework has been simplified in version 3.7.0 to fully use extensions capability..
There are threeto allow to reconfigure the system without any changes to the core: reportDescriptors, reportWorkers and reportGenerators.
Report descriptor extension allow to add new or override existing report definitions. Similarly report workers extension allow to add new or override existing implementations.
Lastly report generator API is now a facade for report generator plugins, which can be defined in report generators extension point. This allows writing custom generators in custom modules without interfering with core code.
Out of the doc the platform now support two kinds of generator plug-ins: PDF and Excel report generators.
Normally storefront would not need custom reports. However there are some cases when a report file needs to be generated. Such as the case with delivery report that can be used for providing customers with downloadable PDF invoice files for the orders they have placed.
Since the report generation is very much dependent on the user journey (i.e. for invoice to be downloaded the customer need to find the order in order history and then click the download PDF button) it makes sense to skip some configurations and provide specific facade functions that encapsulate the programmatic generation of the report file.
Delivery report is fully configured in the CheckoutServiceFacadeImpl.printOrderByReference() method that programmatically creates a report descriptor and then triggers the PDF report generator with this descriptor object and the order object from the order history page.
Resulting file is sent to the output stream thus allowing this method to be used with URL mapping for a downloadable PDF link.
Note that no report worker configuration was needed in this case as we know the exact parameters (i.e. the order number) and we can retrieve the specific order using customerOrderService.findByReference() without the need for a generic report worker.