Promasys has a large set of built-in reports. These reports can be run interactively but they can also be scheduled to run periodically as a background process on the server. Reports can be submitted to this job queue by selecting the “Submit” button instead of the “Run” button when running a report. Next the user has the option to either select a printer as the output destination or a file (e.g. a PDF file) in which case the output will be delivered as an attachment to an e-mail.
If the user selects a printer as the output destination for the report, then this printer needs to be accessible by the server on which the Promasys daemon is running. This implies that the correct printer driver needs to be installed on the server that matches the printer definition and configuration of the user who is submitting the report. If the server has no access to the printer, then the scheduled report will not execute on the server and the Promasys daemon process might terminate unexpectedly.
f the user does not select a printer as the output destination, then the output will be send by e-mail. This requires that the server needs to be enabled and configured for e-mail delivery. The correct configuration depends on how e-mail handling is setup at the site where Promasys is running. The e-mail parameters for this connection can be entered from the Promasys daemon window running on the server.
From the Promasys daemon window, select “Configuration”. In the dialog box that appears, select “Mail Configuration”. A window appears where you can enter the correct parameters for E-mail connection between the Promasys server and your mail system (e.g. SMTP, POP3, IMAP). After configuration of the e-mail parameters, you can schedule a job to test if the output of the report is delivered correctly to your mailbox.
Please remember that the daemon process needs to be running!
If you intend to use the job scheduler to send the report output by e-mail you need to define at least one printer on your server. This is required as the report generator depends on an installed printer driver for the correct layout of the report.
If no printer is defined on your server, then the job scheduler will not be able to run a report and the daemon process will ‘hang’ and eventually terminate with an error.
