[CUBA-component] scheduled reports | preview


i recently worked on a new CUBA app-component called scheduled-reports. It is in preview mode currently. Before releasing it “officially” i would like to get your feedback on it. It is open source (Apache 2 license) and you can find it on github:

If you have any thoughts on that, like bug, feature requests etc. I would love to hear from you.

I’ll just copy over the README.md so you get an impression on what it does:

CUBA Platform Application Component - Scheduled Reports

This application component let’s you schedule reports and execute them periodically.

It allows to define a schedule for a report to be executed. The target report file is stored CUBAs File Storage and additionally optionally can be send out via Email.


  1. scheduled-reports is available in the CUBA marketplace
  2. Select a version of the add-on which is compatible with the platform version used in your project:
Platform Version Add-on Version
7.0.x 0.1.x

The latest version is: Download

Add custom application component to your project:

  • Artifact group: de.diedavids.cuba.scheduledreports
  • Artifact name: scheduledreports-global
  • Version: add-on version
dependencies {


Information on changes that happen through the different versions of the application component can be found in the CHANGELOG.
The Changelog also contains information about breaking changes and tips on how to resolve them.

Supported DBMS

The following databases are supported by this application component:

  • PostgreSQL

Example usage

To see this application component in action, check out this example: cuba-example-using-scheduled-reports.

Using the application component

The scheduled-reports application component enriches the Reports main menu with ability to define Scheduled Reports.

A Scheduled Report consists mainly of a reference to the report instance, that should be executed as well as a schedule that defines on how often the report should be executed.

Emailing Report

Besides the file generation itself, it is also possible to send out the report via email. In order to do this, a Email template can be defined, that includes information on the receivers, the Email subject and body etc. The report file is attached to the email.

Programmatic Scheduled Report Extensions

Currently (v. 0.1.0) the ability to define certain parameters of the Report or the Email template are limited to the abilities of the corresponding application components:

Since there is the need to dynamically define certain information, it is possible to extend the functionality of a scheduled report programmatically that is executed at the point when the scheduled report is run.

In order to enhance a scheduled report programmatically, a Spring bean has to be created in the core module of the application, which implements the ScheduledReportExtension interface.

This interface allows to programmatically define the following options during the execution of a scheduled report:

  • define the report parameter
  • define the report template
  • define the target filename
  • veto right to prevent execution

Application Event: ScheduledReportRun

After the scheduled report was executed, the Spring application event ScheduledReportRun is published. It is possible to register to this application event in order to programmatically use the result of the scheduled report execution.

An example can be found in the example project: BigCustomersListSaver:

public class BigCustomersListSaver implements ApplicationListener<ScheduledReportRun> {

    public static final String NAME = "ceusr_BigCustomersListSaver";

    protected DataManager dataManager;

    public void onApplicationEvent(ScheduledReportRun scheduledReportRun) {

        ScheduledReportExecution reportExecution = scheduledReportRun.getReportExecution();
        String scheduledReportCode = reportExecution.getScheduledReport().getCode();

        if (scheduledReportCode.equals("big-customers")) {
            BigCustomersList bigCustomersList = dataManager.create(BigCustomersList.class);

    private LocalDate toLocalDate(Date dateToConvert) {
        return dateToConvert.toInstant()


Scheduled Report Execution

Every scheduled report execution is logged and can be seen via the menu Reports > Scheduled Reports > Executions. It contains information about the execution timestamp, the report file and optionally a list of outgoing emails and their sending status.


Hi Mario
This is, indeed, an excellent add-on that you have developed.

Quick questions or comments :slight_smile:

1- if you also add week as time dimension that will be useful.

2- option to update parameters automatically and dynamically e.g. sales report generated on 1st June for the month of May.



thanks, appreciate it :+1:

Regarding your first comment:
Yes, makes sense. Will add that in a later version. It can be configured right now via defining a cron expression: 0 0 9 ? * MON *

Regarding your second comment:
This is already possible. The example provided in the example app: GitHub - mariodavid/cuba-example-using-scheduled-reports contains the very same example (if I did not misunderstood you).
In this case the scheduled report extension class is MonthlySalesReportScheduledReportExtension which provides the report parameters dynamically in this method: provideParameters.

Is that what you are talking about?


Hi Mario
That’s great! looking forward for the next version. I’m going to use your add-on to my project, thank you again.

With regards to the second point, it seems that you have what I am talking about, want to test. How can I use that extension, do I have to program it or can be used in the Scheduler at run-time?


I didn’t find this add-on in the Market Place. Isn’t it supposed to be there?


Im not sure what you mean by:

Both are true. It has to be developed and then it can.be used at runtime.

You can find it in the marketplace: Scheduled Reports – CUBA Platform


Thanks I know that link but what I don’t see is from CUBA Studio Market Place link:

i think in studio there is a filter for your CUBA version. Not sure which version you use. Scheduled records is currently 7.0.x only.


I’m using the most recent versions of both Studio and Platform I.e. 7.1


you can now schedule reports and automatically send them through email with the scheduled-reports addon for @CubaPlatform also for version 7.1. It is now available in version 0.2.0. Check it out here: GitHub - mariodavid/cuba-component-scheduled-reports: CUBA component that let's you schedule reports and execute them periodically


Hi Mario
Thanks. I wonder why this is still not visible from the Studio. Most likely the studio is filtering by v.7.1.1 (as you will see in the footnote), do you see it from the latest version of the Studio ?

I have added the dependency to the gradle file manually as follows, it has successfully deployed without any error but I don;t see the add-on menu in my application.


Hi Mario,
This looks like a great tool and is exactly what I need for my app. We’re now at 7.2 (7.2.16 to be precise) with the platform and although I can install it without error it won’t run without error. Are you planning to make this work with 7.2.x?

Hi @gb91757,

back then there was an error with CUBA 7.2, which is already solved. I merged an existing PR which did the update to 7.2.

So I expect it to work. That being said, since Bintray is down and I have not thought about a new way of distributing releases yet, you need to fetch the sources from the master branch: GitHub - mariodavid/cuba-component-scheduled-reports: CUBA component that let's you schedule reports and execute them periodically and do a manual gradle build to get the artifact into your local gradle cache or if you use a dedicated Artifactory repo, then you can also push it there.


Thank you for the response. As the market place showed the version as 7.1 I just assumed it was no longer getting updated and thought maybe you’d retired :grinning: or something so I went ahead and did what you suggested and after I built it myself from source etc it seems to be working (although I haven’t fully tested it yet). I should have posted back here what I had done much sooner - sorry for that.