Scheduling a report with cached report bursting

You can schedule a report with cached report bursting as a normal report. However, there are some differences between the formats in which the report is to be published.

Scheduling to HTML/Page Report Result to version

When you schedule a task to publish a report with cached report bursting to the HTML and/or Page Report Result formats to the versioning system, the scheduled result depends on the mode which is controlled by the property server.enable.cachedreportbursting in server.properties in <install_root>\bin:

When server.enable.cachedreportbursting=true which is the default, JReport will create a report result with the report data for all possible users. This allows the report to run with a single query to the DBMS to create the report for all users in one pass. It is similar to report bursting, however, report bursting does not support the Page Report Result format and it makes a separate physical report result for each user and the administrator needs to manually restrict access to the result. When a user views the report result using cached report bursting, JReport Server will use the security identifier of the user to restrict access to the data in the report to the specific groups the security identifier is allowed to view. The end result is the same as the bursting report in that the user sees only his data, the advantage to the administrator is there is only one version result to manage. Users can perform interactive actions on the scheduled page report result as on other page report result, and the formulas, summaries and other similar data will be recalculated based on the privileged data.

Note: If the report is cached report bursting and RLS/CLS mixed, then when other users other than the user who did the scheduling view the scheduled HTML result, a blank page is displayed.
When server.enable.cachedreportbursting=false, the scheduled result only contains the data that the user who did the scheduling is allowed to see. This is primarily for compatibility with pre-8.2 versions of JReport. In this case, "to page report result" is not supported.

Scheduling to e-mail

When you schedule a report with cached report bursting to publish it to e-mail, there is a slight difference. JReport Server supports a multiple mail feature which enables sending the data result directly to each user who is authorized to view the report.

Assuming that the catalog and the report have been published to JReport Server, and two users admin and jennifer both have the permission to view the report. The following procedure shows how to schedule a task on a report with cached report bursting to be published to e-mail.

Access the JReport Console page with user ID admin or jennifer.
Browse to the row that the report is in, put the mouse pointer over the report row and click the Schedule button on the floating toolbar.
In the General tab, select the report tab with cached report bursting.
In the Publish tab, switch to the To E-mail sub tab and then check This report has Cached Report Bursting. E-mail the report to each specified user.
Type the subject and select the result format, then click Finish.

JReport Server will get the e-mail addresses from the user accounts, and then send the report result to admin and jennifer, with the contents in accord with their access right to the report.

Note: Before publishing to e-mail, make sure you have input the e-mail addresses of the users when configuring JReport Server. To do this:

Access the JReport Administration page, click Security on the system toolbar, and then select User from the drop-down menu.
In the User panel, choose the user name that you want to edit in the User ID column, and then click it. You can then type in the e-mail address of the user.

Scheduling to other formats

When scheduling a report with cached report bursting to other formats, the scheduled result only contains the report data that the user who does the schedule is allowed to see. All users will see the same data as the scheduling person.