Batch
- Log files are now 100% unique per start of Report Runner Batch. Previously, JNRRBLOG.TXT was always the "current" log file. This has changed. The problem with JNRRBLOG.TXT always being the current log file was if more than one batch was running at the same time, the same log file got written to by multiple batches. This can no longer happen. And when you go to the Debugging menu to view the current log file, it will open your current "unique" log file.
- Additional feature added to the Notification Report to automatically add the debug log file for the batch if the batch does not run successfully. This automatic behaviour can be modified using a new INI setting under [Options] called AttachLogFileToNotificationReport=NO (it is YES by default). To automatically attach the log file to the Notification Report for successful batches, too, add AttachLogFileToNotificationReportOnBadRunsOnly=NO (it is YES by default).
- Additional feature added to the Notification Report for reporting issues with bursting batches, too. We now have a bursting exceptions log file that will be automatically appended to the Notification Report. To modify this behaviour, under [Options], add AttachBurstExceptionsLogFileToNotificationReport=NO (it is YES by default). This new feature to report burst exceptions is great, especially when used with the batch-specific INI setting of NoFailOnBurst=YES. This allows your burst to fully run, even with exceptions, and you can handle the exceptions in the end. If you do not turn on NoFailOnBurst=YES, a bursting batch will stop running on the first exception.
- Fixed a bug where bursting batches being exported to mail... if an error was encountered, the batch would fail, but the message would still say "Successful" as the last run message. This has been modified to say "Mail Error... check log file".
- Added an error catch for users trying to (erroneously) open RPT files instead of XML batch files using the Open button. This would previously cause the application to crash and send us a ticket.
- Added executable version and path information to log file when debugging is turned on from Debug menu. This information has always been available when debugging was on from the start, but the log was incomplete when debugging was turned on after application was running.
- Added "ref=" parameters to Jeff-Net URLs opened from within the application
- Disabled CC and BCC settings from being applied to the Notification Report for bursting batches
Viewer
- Log files are now 100% unique per start of Report Runner Viewer. Previously, JNRRVLOG.TXT was always the "current" log file. This has changed. The problem with JNRRVLOG.TXT always being the current log file was if more than one user was running reports on a shared server at the same time, the same log file got written to by multiple users. This can no longer happen. And when you go to the Debugging menu to view the current log file, it will open your current "unique" log file.
- Added executable version and path information to log file when debugging is turned on from Debug menu. This information has always been available when debugging was on from the start, but the log was incomplete when debugging was turned on after application was running.
- Added "ref=" parameters to Jeff-Net URLs opened from within the application
- Fixed a random bug where the directories/folders were not always being sorted alphabetically for all drives in the left-side directory/folder view.
---
This is not a critical update, but it is highly recommended!
http://www.reportrunner.com/download.htm
