We're updating the issue view to help you get more done. 

Scheduled reporting

Description

From https://openvpms.org/project/scheduled-reporting

This project will enable reports normally run through the Reporting|Reports workspace to be scheduled to run automatically using the Quartz scheduling support.

This will be configured via the Administration|Organisation workspace, using a "Job Configuration: Reporting" configuration archetype.

This will use cron-like syntax to specify the day/time when the job should be run.

It will also include fields to determine how the report will be output, i.e. to:

  • file

  • printer

  • email

File Output

When file output is selected, the following fields specify the location and type of the output file:

  • directory

  • file type (.csv, .pdf)

  • file name. If no extension is provided, the file type determines the extension

If the report template has a File Name Format, this will be used to generate the file name. This can be used to append a date/time to the file name for example.

If the file exists, it will be overwritten.

When print output is selected, the following fields specify the printer location:

  • location. The practice location. This is constrained to those locations specified by the report document template.

The interactive flag specified by the template's Document Template Printer will be ignored.

Email Output

When email output is selected, the following fields apply:

  • from - the from email address. Defaults to the email address of the current user

  • to - the email address to mail to. Defaults to the email address of the current user

  • file type (.csv, .pdf)

  • file name. If no extension is provided, the file type determines the extension

If the report template has a File Name Format, this will be used to generate the file name. This can be used to append a date/time to the file name for example.

Report Parameters

Available report parameters will be determined from the report.

Values for these parameters will be configurable, but the values must be string constants. Up to 5 parameters will be supported.

Dynamic parameter values, evaluated via an expression, can be handled as a separate project.

Permissions

The Run As configuration determines the user that the report is run as. This user must have appropriate permissions to execute the report.

Logging

On completion/failure of the job, a system message will be sent to the Run As user.

Environment

None

Status

Assignee

Tim Anderson

Reporter

Tim Anderson

Labels

None

Components

Fix versions

Priority

Minor