Salesforce

WorldServer - How to Schedule a Report via Jasper Reports

« Go Back

Information

 
Article TypeSolution Article
Scope/EnvironmentWorldServer
Symptoms/Context
Loading a Jasper Report might take a long time to return when running it via the User Interface and sometimes it is not returning at all or timing out. Is there a way to avoid waiting for the report to finish running?
Resolution
Some custom reports can be collecting a high amount of data and do many calculations for certain fields. This would cause the report to take a long time to generate so it is much better to perform this in the background by scheduling a report. Instead of running a Report manually, you can schedule the creation of a Report. This video from Jaspersoft explains how to create, modify and schedule reports in Jasper Reports (the tool used by WorldServer. 

You can also follow these steps.

1- Right-click the chosen report and click Schedule

rc1

Choose either Run Now or Create Schedule

rc2
You will see two options:

Run Now = Execute the Report in the background straight away
Create Schedule = Execute the Report on a chosen schedule.

2- For the Create Schedule option you would now be asked to choose the Schedule:

rc3

It can be executed hourly, daily, weekly etc., and on a specific date.

3- Next, go to the Parameters tab. This may be blank if the report takes zero parameters:

rc4

4- The 3rd tab is the Output options such as file format:

rc5

5- The final tab is for Notifications. This is important if the report needs to be emailed out, it is also important to notify an email if the report fails to run.

6- Please check the box to Include Report Job Information and Stack Trace as this is useful for the Support Department. 


rc6

6- When all is completed, click Save to begin the Schedule.
 
Root Cause
Some custom reports can be collecting a high amount of data and do many calculations for certain fields. This would cause the report to take a long time to generate so it is much better to perform this in the background by scheduling a report.
Reference
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by