Report Bursting
Report bursting enables you to schedule and distribute a single page report to multiple users who each receive a subset of the results related only to them. This greatly reduces administrative burden and runtime load, because you don't have to run a report a million times in order to get a million results. You can also schedule a bursting task at a low-load time to reduce performance impact. Report can distribute the bursting report results to any destination, including email, FTP, disk, and the versioning system and users in the security system of Server.
To create a bursting report, first the report designer needs to create a recipient query. The query should contain data fields that define recipients and a secondary data field that can be mapped to the bursting key, which is the field distinguishing how the report data is to be split. The report data is therefore split by the bursting key and then distributed to the recipients in the query according to the mapping relationship.
See Creating Bursting Reports in the Report Designer Guide for more information.
In the following example, we define a bursting schema in a page report to split the report data according to regions and distribute the report to the versioning system of Server. After publishing the catalog and report to Server, we can schedule a task to distribute the bursting results.
Back to top