Hi Eric,

If I understand correctly, you want to send attachments along with your email body. In the advanced section of our configuration, there's an option that allows you to attach files.

 If you are using an earlier release, you may add this configuration under the "Other Settings" section.

allowarcscriptinattachmentmode = True

Please make sure to run the connector in attachment mode instead of template.

Just to be clear, my Input document to the Email Send connector looks like this:

<Items>
 <Name>Joe Dirt</Name>
 <OrderNum>0032112</OrderNum>
 <Invoice>JD0246</Invoice>
 <File>JD0246.pdf</File>
</Items

If I use Attachment mode, Arc will attach the above XML file to the email.

I’m currently running 2023 - 23.3.8725.0 and don’t see the above checkbox so I assume I will need to use the snip for “Other Settings”.

My question is:  where does the ArcScript go to locate and attach the file in expath(File)] (I know where logical path to the file location)?  Would I use the Before Send event?

Thanks

Hi Eric,

If you are using an earlier release, you will need to configure the settings under other settings.

In attachment mode, you can write the script within the settings tab of the connector, and the file passed through the input will be sent as an attachment.

Here is an example: I am sending the filename as the body of the email along with the attachment.

Test email received:

Hi Eric, 

The EmailSend connector wouldn’t be the right one for this task as you present it now - you can evaluate the message as a template using the template mode, and attach the message file (in this case, the xml file), but you cannot dynamically evaluate additional attachments to the EmailSend connector. 

If you had a flow that picked up and processed the PDF file itself, and sent that to the EmailSend connector in Attachment mode, that would send your PDF - and if you included all of the other metadata as headers on the messages in Arc, reversing your message structure:

https://cdn.cdata.com/help/AZJ/mft/Architecture.html#message-headers

Then you could send your PDF in attachment mode, and use the allowarcscriptinattachmentmode as Lohith mentions to dynamically render those elements in the headers in the body: 

If you do that, you could use a script to parse your XML and output the PDF referenced in it with additional headers. Assuming that you have these PDF’s in a static folder, something like this would work:

<!-- Parse the XML -->
<arc:set attr="xml.uri" value="uFilepath]" />
<arc:set attr="xml.map:name" value="/Items/Name" />
<arc:set attr="xml.map:ordernum" value="/Items/OrderNum" />
<arc:set attr="xml.map:Invoice" value="/Items/Invoice" />
<arc:set attr="xml.map:file" value="/Items/File" />
<arc:call op="xmlDOMGet" item="xml">
  <arc:set attr="output.header:name" value="axml.name]" />
  <arc:set attr="output.header:ordernum" value="nxml.ordernum]" />
  <arc:set attr="output.header:Invoice" value="ixml.Invoice]" />
  <arc:set attr="output.header:file" value="ixml.file]" />
  <!-- Reference the filepath for output -->
  <arc:set attr="output.filepath" value="C:\\Users\\JamesBlasingame\\OneDrive - CData Software\\Documents\\\xml.file]" />
</arc:call>

<arc:push item="output" />

Alternately, there is an operation that will send an email using the default email settings for notifications, appSendEmail:

https://cdn.cdata.com/help/AZJ/mft/op_appSendEmail.html

This supports attachment arguments, but it’s not as easy to review for errors as the appSendEmail operation.