Table of Contents |
---|
Overview
YC provides a flexible mechanism to create report plugins that will naturally fit into existing report wizard interface, thus system integrator only need to concentrate on the business functionality around generating specific report.
...
- 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
Extension points
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 to naturally be included in the application.
...
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.
Admin app
Custom implementation
Warning | ||||||
---|---|---|---|---|---|---|
this feature is deprecated in version
|
...
Out of the doc the platform now support two kinds of generator plug-ins: PDF and Excel report generators.
Storefront
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.
...