Description Usage Arguments Value Examples
Parses inputs from a message saved when the e-mail client run its rules. Parser is looking for UseModel, UseScript, or UseReport follow by a number (ID) associated with Model, Script, or Report. For reports and scripts there is also the option to supply comma separated data.
1 | MailTriggerInput(InputPath)
|
InputPath |
string, path to a saved e-mail message from your e-mail client Likely filenames in the [TriggerPath] are modelInput.txt, ScriptInput.txt, or ReportInput.txt |
list, ID, integer ID of the model, script, or report selected. data, data.frame of any supplied inputs.
1 2 3 4 5 6 7 8 | #################################
# Get E-mail Trigger Input #
#################################
## The file is a saved e-mail message from your e-mail client
MDL_Input <- MailTriggerInput(InputPath="c:/triggers/modelInput.txt")
SCRPT_Input <- MailTriggerInput(InputPath="c:/triggers/ScriptInput.txt")
RPT_Input <- MailTriggerInput(InputPath="c:/triggers/ReportInput.txt")
|
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.