Video Screencast Help

Automation Policy to send a report as an attachment to an email

Created: 14 Dec 2012 | 2 comments
alcer123's picture
10 Agree
0 Disagree
+10 10 Votes
Login to vote

As of today, 12/14/2012, there is no way of sending a report as an attachment to an email account, in SMP 7.1. It is possible to send the results of a report as a data set in the body of an email with the Policy "Send automated report email,"  and it will send a nicely formated HTML data set, but not option for an attachment. It will be perfect if we just have to select the Send as an Attachment from the pull down menu Report URL, under the Job/Task Input Parameter window, as shown in Picture attached.

Hasta ahora, 14/12/2012, no hay manera de mandar un reporte vía una Automation Policy en SMP 7.1, como un archivo agregado. Es posible mandar los resultados de un reporte en el cuerpo del email usando la Policy "Send automated report email," que mandara una tabla formateada de datos del reporte, pero no es posible mandarlo como un archivo. Seria perfecto si se pudiera seleccionar del menú del Report URL que esta en la ventana de Job/Task Input Parameters, como se observa en la figura agregada a esta nota.

Comments 2 CommentsJump to latest comment

JoeVan's picture

Still a limitation in the current (7.5 SP1) platform.  :(

Joe VanHollebeke
Systems Engineer

Login to vote
Juri Zenkevits's picture


We are working to include the extended email body syntax for attachment definition in 7.6 (and probably in 7.5.HF6).

By this syntax, there would be no UI changes required, but task definition can be adjusted so customer can specify, what part of the (formatted, with all token/macro replacements done) text will go to attachemnt, and what would be a body.

Something like this

<!-- SMP:ATTACHMENT:report.htm -->


<!-- SMP:FILE:c:\eula\something.txt -->

<!-- SMP:BODY -->

<html><body>Attached report for %!message!% computers.</body></html>


This sample will create email with 2 attachments: one is report results, one is just a file from somewhere on NS machine harddrive. 

Body will tell the short message.

Hope, this will be sufficient to quickly solve the request without changing much all around NS web pages and tasks.

ps. this approach will work for any place in ITMS, which sends email - the final attachment markers are detected on the core level of API and will be effective for everything.

Login to vote