email with attachment

Oct 12, 2012

Hi everyone,

I am trying to include a file as an attachment to an email. Here is the syntax that I am using

mailto:abc@xyz.com?subject=hello&body=here is the attachment&Attachment="./filename.doc"

But when I try this in the Storyline "Jump to URL/FIle", the attachment part doesn't work. Is there anything wrong with the syntax? Any suggestions are welcome. Thanks in advance.

2 Replies
Justin Grenier

Good Afternoon, Benny.

Does this work on other web pages?  I don't think Storyline is handling mailto: links in a particularly special manner, so I would expect to see the same functionality from Storyline.

Where are you expecting the "./filename.doc" file to reside?  If mailto: links support attachments (and I'm not certain they do) I believe the browser will interpret this link as a reference to a file stored on the user's local machine--not a file stored on the machine that is hosting the page.


If this is what you want, and you are expecting that all of your learners will have a file called "filename.doc" that resides in their "My Documents" folder, for example, could you use an absolute path rather than a relative path (since various browsers might interpret the "./" differently), as in:

&Attachment="%USERPROFILE%\Documents\filename.doc"

I can't imagine that a mailto: link would  be able to attach a file stored on the machine that is hosting the webpage.  However, if the file is publicly accessible from a URL, why not do the following instead?

mailto:abc@xyz.com?subject=hello&body=here is the file you need:  http://www.mysite.com/files/filename.doc

Benny Kurniawan

Hi Justin,

The file will be residing on the same site (folder) hosting the Storyline interaction. We want user to be able to load the email client (e.g., Outlook) and include a file as attachment. This is the reason why we are thinking to use "mailto:___" instead of "http://___".  Though we might have to create two buttons. I have checked the mailto syntax and apparently it does not support "Attachment". Sigh ;(

This discussion is closed. You can start a new discussion or contact Articulate Support.