The report scheduler appears to work by serializing a
scheduled report object to the quartz scheduling
table. This makes it very difficult for an external
applications (and impossible for non-java apps) to
schedule a report via the database.
A simple solution would be an action like the
ExecuteReportAction that allows single-step
scheduling of a report. It would in fact work
exactly like ExecuteReportAction, but finish by
scheduling the report instead of filling it.
I am working on a similar solution to tide me over
until this is included in one of the releases. If
you think it would be helpful, let me know and I can
send you my code.
Thanks again for the wonderful application!
Log in to post a comment.