[Email:]
Specifies the start of an e-mail section.
Macro Compatibility
The macro can be used in all input document types and in Report Studio.
Usage
The [Email:] macro can be used to email (in HTML format) the portion of the Word document contained therein, including text, charts, tables, etc. All images are embedded inline. Any email address used may include an optional display name, in which case the email address (person@domain) must be specified inside angle brackets, e.g. 'Bob Smith
Parameter | Type | Presence | Purpose | Options | Default |
---|---|---|---|---|---|
String | Mandatory | The e-mail subject. | N/A | N/A | |
List<String> | Mandatory | A semicolon-separated list of e-mail addresses. | N/A | N/A | |
List<String> | Optional | A semicolon-separated list of e-mail addresses. | N/A | N/A | |
String | Optional | The email body text. This will never appear in the actual report, just in the email. Format this as HTML. For the [EmailReport:] macro, this is the entire body. For the [Email:] macro, this is used to prefix the content between the [Email:] and [EndEmail:] macros. | N/A | N/A | |
List<String> | Optional | A semicolon-separated list of e-mail addresses. | N/A | N/A | |
String | Optional | Add a comment to make your document template more readable. The comment is discarded in the output document. | N/A | N/A | |
String | Optional | The name of the Connection. | N/A | N/A | |
String | Optional | The optional display name (shown in your email application) of the sender. NOTE: you can ONLY change the display name when you have specified a Connection e.g. with the 'connectionName' parameter or in the Configuration JSON section of the Connection. Otherwise email sending uses ReportMagic's default SMTP client and the display name is set by the system. | N/A | N/A | |
Boolean | Optional | Should NCalc expression evaluation throw error on Overflow |
|
true | |
String | Optional | The text to display should the macro fail to execute. Note that a poorly-specified macro (e.g. omitting mandatory parameters) will still result in an error message. | N/A | N/A | |
String | Optional | A single e-mail address. This may not be supported by your email server (i.e. setting the sender to an arbitrary email), and can be omitted to use the default. When the email server does NOT support this, you may receive a System Error when processing the report, so you should check first by testing the macro. NOTE: you can ONLY change the from address when you have specified a Connection e.g. with the 'connectionName' parameter or in the Configuration JSON section of the Connection. Otherwise email sending uses ReportMagic's default SMTP client and the from address is set by the system. In other words, if you set the from address, you must set a Connection, and the email address does NOT need to have been set up anywhere else (you can choose any email but your mail server may not support it). | N/A | N/A | |
Boolean | Optional | Whether the section of the Word document contained inside the macro should be removed in the final output document (does not affect e-mail content). |
|
false | |
String | Optional | The condition that must be true in order for the macro to be executed/evaluated. Must either evaluate to true or false, for example: "3+5=8" or "contains('abcd', 'z'). | N/A | true | |
MacroMode | Optional | The mode in which variables are stored. In the legacy mode (default for Schedules), the variable created is a string and formatted. In the normal mode (default for Report Studio), the output variable is stored as a strongly-typed object, e.g. an Int32 or a List |
|
Legacy | |
ObfuscationType | Optional | Obfuscation type. Use obfuscation to write reports where sensitive data is hidden. When used, ReportMagic guarantees that the same input string will map to the same output string for the whole of the report (but the next time the report runs, it will most likely map to a different value). If you use obfuscation, the property in your macro will not show up and instead, you will see a fake item of the obfuscation type chosen. |
|
None | |
String | Optional | The e-mail priority. |
|
normal | |
String | Optional | If specified, adds a warning message for this macro. This is processed as an NCalc, and the warning message will ALWAYS be present and will be the value of the evaluated NCalc expression. | N/A | N/A |
Examples (7)
Example 1:
[Email: subject=Test Email, to=bob.smith@mycompany.com;david.brown@mycompany.com, priority=low]Some content[EndEmail:]
Example 2:
In this example, set the from address and display name:
[Email: subject=Test Email, to=bob.smith@mycompany.com, from=bobsmanager@mycompany.com,displayName=BIG BOB]Some content[EndEmail:]
Example 3:
[Email: subject=Pay Rise, to=bob.smith@mycompany.com, cc=hr@mycompany.com;accounts@mycompany.com, priority=high]Some content[EndEmail:]
Example 4:
Here, the body text appears in the email, but not in the report:
[Email: subject=Latest Chart, to=bob.smith@mycompany.com, body=Here's the latest chart, Bob.] [LogicMonitor.Graph:device=dev.panoramicdata.com,graphName=CPU Usage,dataSourceName=WinCPU] [EndEmail:]
Example 5:
[Email:subject=Latest Charts,to=bob.smith@mycompany.com] Here are the latest charts, Bob: Graph 1 (server 1): [LogicMonitor.Graph: device=dev.panoramicdata.com, graphName=CPU Usage, dataSourceName=WinCPU] Graph 2 (server 2): [LogicMonitor.Graph: device=test.panoramicdata.com, graphName=CPU Usage, dataSourceName=WinCPU] [EndEmail:]
Example 6:
[Email: subject=Using the hidden parameter in Email macros, to=bob.smith@mycompany.com, hidden=true] This content will be included in the email, but not in the output documents, by using "hidden=true". [EndEmail:]
Example 7:
[Email:subject=Your DataCentre Performance Email, to=bob@mycompany.com, priority=low, body="Hi Bob,<br />Here are the details of this month's performance.<br />Best Wishes,<br />Ethan Cole"] <The rest of the report showing performance and which is included both in the email and in the repot goes here> [EndEmail:]