In release 2013.90, we developed scheduling reports and added them to our System Reports directory. Our System Reports (End of Batch Notification, Batch Message, and now these scheduling reports) get installed with the full installer, but not the updater (we are very careful about what we do with the updater). This article explains how to install\update and use your System Reports at any time.
Assuming your software is up-to-date, the reports are located here:
<path to Jeff-Net documents folder
>\Report Runner Batch\AppData\System Reports
If you do not have the reports, contact us via opening a support ticket
, or re-run the FULL installer (you do not need to uninstall anything).
After installing or updating your system reports, you should have the following reports:
- Batch Message Report.rpt
- End of Batch Notification Report.rpt
- jnSchedulesReportDataFile1.csv (not a report, but a data work file)
- Schedule Forecasting Report.rpt
- Scheduling Information Report.rpt
- Scheduling Last Run Report.rpt
- Twitter Post by Day of Week.rpt
Batch Message Report
This report is used for simple SHORT messages. These messages can be inserted into the body of an email or used to send an SMS text. This report is extremely simple. There is no data source. It accepts one single parameter that IS the data of the report (ie. a message to communicate). You can enter a something manually or you can use any of the built-in parameters values that also have variables that get replaced at runtime. For example, some of the parameters have variables to tell you what the batch file name is and what the ending status of the batch is/was. An example of another use of this report would be... imagine running a month end process of reports. At the end of that batch, you would add this report, set the output type to SMS, enter your phone number, and set the parameter to say "Month End Processing Complete". This report can be used to communicate anything you want it to.
End of Batch Notification Report
This report has been around since the creation of Report Runner Batch. This report can be added to any batch. It will always run as the last job in the report (no matter when you add it), and it will show you either all the jobs in a batch with start and end times or it will show you errors only (these options are controlled via a parameter value). You will notice when you add this report to a batch, the job window will automatically check the option at the bottom of the window to Use Notification Database. You might ask why we even show this as an option if this always does this. Good question. We do it, because a number of customers have modified this notification report and saved it under a different report name. If they still want it to work correctly, you have to check/select to use the notification database. That causes Report Runner Batch to pass a special data file at the end of the batch that stores jobs, start times, end times, etc.
Before we explain what each report does, understand first that there is a bit of data "magic" with these reports. There are no ID or passwords to set for these reports.
Just add them into a batch
(one or all scheduling reports --- doesn't matter), and when Report Runner Batch runs them, it will automatically re-build all necessary scheduling data on-the-fly and report it back to you. As Steve Jobs would have put it... "it just works". These scheduling reports have parameters that can control how much and what level of detail to include in the report. Note, the scheduling reports have parameters to run them different ways. The parameter options are available by clicking the [CHOICES] button. Do NOT use the drop-down settings, as those are the Global Expressions and Constants and do not apply here.
* Schedule Forecasting Reports
This report will analyze the Windows Scheduler and show you all batches/schedules that will be running in the future.
* Scheduling Information Report
This report will show you each batch file scheduled and jobs/reports within the batch.
* Scheduling Last Run Report
This report will show you just what you think... the last time a schedule ran.
Twitter Post by Day of Week
This report is a sample report to show you how you could post a different message or output different data based on the day of the week. This would be especially useful for posting different messages to Twitter on a daily basis, but you would only schedule this one report/job to run daily, and the information would change every day.
Testing Reports Folder
Note, there is a folder in the System Reports directory called Testing Reports. This folder has one single report that connects to a sample MDB database. This is used for consistent testing should Report Runner Batch ever have any kind of problems running a report after installing. It allows Support to have a sample report that we KNOW works and test with it. We also use it for demonstration purposes of Report Runner Batch.
How To Modify The End Of Batch Notification Report So Zero Records Is Not An Error