...
Email Report Processors have 2 types of configuration settings needed to work - they need global settings (stored in global properties/ formerly Global Properties from 1.9 downwards) in order to configure the actual ability to send emails. Then, each Processor needs to be configured with the content of the email message.
...
Settings
The following global properties settings must be set to appropriate values. The values specified below are the defaults that will be used if no configured global property settings value is found:
- mail.transport._protocol=smtp
- mail.smtp_host=localhost
- mail.smtp_port=25
- mail.smtp_auth=false
- mail.debug=false
- mail.from=
- mail.user=
- mail.password=
...
Property | Description |
---|---|
from | The email address that the message should come from |
to | The email address(es) that the message should be sent to. Multiple addresses separated by commas. |
subject | The subject line for the message |
content | Any raw content that should go in the body of the message |
addOutputToContent | If the rendered report is text, setting this to true will include it in the body of the email |
addOutputAsAttachment | Any rendered report can be included as an attachment to the email message by setting this to true |
attachmentName | If addOutputAsAttachment=true, this can be used to specify the name of the attachment on the email |
Example Configuration:
Code Block |
---|
to=someone@hashaiti.org
from=openmrs@hashaiti.org
content=Please see the report attached.
subject=Ward Audit Report
addOutputAsAttachment=true
attachmentName=wardaudit.xls
|