Scott Andersen

The “Report Execution” link normally displays the target report in JasperReports Server’s interactive viewer UI. If instead you want the target to be displayed in your UI, you can use visualize.js to capture the link event coming from the Studio report and redirect it to the appropriate report. When implementing drill down reporting in visualize.js, you must map the parameters from the captured event link (link.parameters) to the targeted report’s parameters. These link parameters are defined when creating the hyperlink in Jaspersoft Studio. Typically the mapping of parameters is very specific between the source-master and target-slave reports. But what if there are different links coming from the report? Rather than implementing complex logic in the link event handler, another approach is to draw both the target report url and the parameters from the link and generate the parameter mapping dynamically. Some assumptions: The parameter names in the master parameter mapping (in the Hyperlink properties) match the input parameters of the slave report. This example uses the following “Sample” reports provided in JasperReports Server deployment. “13. Top Fives Report” – this report has links to two different reports:“09. Customer Details Report” – linked to from the “Customers” list, passing the customerId.“12. {Promotions Detail Report” – Linked from the “Promotions” list, passing the promotionId.Within the embedded-in web page javascript, do the following: Define a “createReport” function, passing in the report path and the report parameters. Define a function to format the parameter list based on the passed parameter JSON. The “link.parameters” cannot be used directly, since the visualize.js parameter requires values be included in an array, and Studio links map content differently depending on the type of parameter passed (string vs collection). That is why a “buildParms” function is required. Populate the <div> with the initial report. Use the “createReport” function in the link event handler to create the target report, based on the information from the link.This example provides a simple implementation of a dynamic parameter generation in visualize.js. Sample drilldown web page is attached below. drilldownreport.html drilldownreport.html_0.txt

Report bursting is the process of running a report once and then dividing the results for recipients who each view a subset of the data. In the past, report bursting in Jaspersoft has been accomplished using external tools interfacing with Jaspersoft’s REST services. With release 8.1, Jaspersoft introduces report bursting capability into Jaspersoft, using existing features of Jaspersoft Studio (scriptlets) and JasperReports Server (scheduler). This article walks through the creation of a bursting job. Assumptions: The target or “bursted’ report exists, and requires an input parameter that identifies what the report is for. In the example I used the “6. Profit Detail” report provided in the JasperReports Server Samples, which shows the Profit based on ProductFamily.Create a “bursting” report. This is the report that will drive the report bursting process.The report does not require anything to be displayed; however, putting together a simple display can record what detailed reports were generated.Write a query that returns the values required for bursting the report. This may include: The id or values that will control the generation of individual reports. (required)Emails, locations, or other criteria to uniquely identify the results and the distribution of the results.Add the “Bursting Scriptlet” to the report by right clicking on “Scriptlets” in the Outline of the report and selecting “Create Bursting Scriptlet”. Edit the bursting scriptlet settings using the wizard. To access the wizard, right click on the Bursting Scriptlet in the outline and selecting "Edit Bursting Properties". There are several sections that can be filled in to control the bursting of the report. If you notice, the settings have corresponding settings in the JRS Scheduler UI. Check the Scheduler documentation in the JasperReports Server User Guide for details of what these various options do.Note that multiple settings have “Expression Editors” associated with them. These can use values from your master query to control the bursting. The following are the minimum options that must be entered to create a basic bursting job. Essential Options: Server Profile – This is the connection to the server (defined in the “Repository Browser”) that will be used to populate various lists in the wizard.Enabled – this defaults to “false” so you can test the basic execution of the report. Changing this to “true” will cause the bursting to execute when you preview the report.Job Label – The name of the job that will appear in the Schedule manager.Job Description – The description of the job that will appear in the Schedule manager.Report UI – The path to the report that will be bursted. In our scenario we will be executing the “6. Profit Detail Report” in the server. You can use the folder browser to connect to the JasperReports Server identified previously to navigate to the report, or you directly enter the report path.Server data adapter - This is optional but needed if you want to test the bursting job from Jaspersoft Studio. It is an exported JR data adapter file and can be created by following the additional instructions below. Output File OptionsFile name - the base file name for the individual results (do not use spaces or dots in the name) Description – The description of the result (if the result is saved into JRS repository).Formats – the format of the result filesOverwrite Files - if the file name of the existing file is the same - defaults to trueSequential File Name by Timestamp - defaults to false. If true, provide a "Timestamp Pattern".Output to repository – send the results to the repository.Repository Folder URI – the location in the repository where the results are saved. You can use the folder browser to connect to the JasperReports Server identified previously to navigate to the folder, or you directly enter the folder path.Additional options can be added for FTP Options, Job Run Notifications, and Job Status Notifications. Next, connect the parameters in the bursted report with associated values from the bursting report's query: Click on the “Parameters” tab and enter the parameters needed by the bursted report.Parameter name – the name of the parameter as defined in the bursted reportParameter value – the value to be sent to the bursted report. Using the Expression Editor you can tie this to a field coming from the bursting report’s query.Once created, the report can be tested from Studio (if a server data adapter was provided), or published and executed on the server. Creating a JasperReports Server data adapter file.Create a Data Adapter Export to your workspace. Reference that file in the Bursting wizard.