Altova MobileTogether Designer

The XPath expressions for these two settings (the message's title and body text) can either be a string or can generate the respective texts from XML page sources.

In the screenshot above, the XPath expression for the Title field is a directly entered string, while the expression for the body text returns the content of the Location/@Geolocation node. This node provides the geolocation coordinates of the mobile device, which were obtained by using the Start/Stop Geo Tracking and Read Geo Data actions (see screenshot above).

Note:  On iOS, the HTML/text selection has no effect; some apps might automatically interpret an existing html flag correctly.

Files and images can be attached to the message. You can select one of three options for attachments:

•No attachments (selected by default)

•Attachments listed below

•Dynamic attachments

Note: Note the following points for Windows Phone and Windows App clients: Windows Phone supports attachments; Windows 8.1 does not. On Windows 10, the default Outlook Mail client that is installed with the OS supports attachments, but if Microsoft Outlook is the default mail client, then attachments are not supported.

Attachments listed below

This option allows attachments to be created individually. To add a new attachment, click . The screenshot below shows a message with two attachments. To delete an attachment, click its Delete icon.

Each attachment has the following properties:

•Filename (XPath): The filename can have any extension. The filename serves solely as a representation (in the message) of the attachment; it is not an actual path.

•Content (XPath): You can select an XML tree fragment, a single XML node, the text content of one or more nodes, or you can directly enter a string that will be the content of the attached file. The content will be parsed according to the selection in the (next) Content type property.

•Content type (combo box: XML/Base64/Text): If the content type is XML, then the content that is selected via the Content property (previous property) is parsed as XML data: an XML nodeset is expected, and the nodeset will be attached to the email. If the content type is Base64, then Base64-encoded content is expected, and this content is decoded. So, if the content is a Base64-encoding of an image, then an image is generated and attached to the email. If the content type is Text, then text is expected as content, and this text will be attached to the email. Note that the value of the Content property must be readable according to the selection made for the Content type property.

Dynamic attachments

The XPath expression uses the mt-email-attachment XPath extension function to create the attachments.

mt-email-attachment

mt-email-attachment(Filename as xs:string, Content as item(), ContentType as xs:string) as array(*) Prepares the XML, Base64, or text content that is provided by the Content argument as an email attachment. Whether the content is parsed as XML or Base64 or text is determined by the ContentType argument, which takes either XML, Base64, or text as its value. The filename that is associated with the attachment is given by the Filename argument.   Note:  The mt-email-attachment is a requirement when using the Dynamic Attachments option of the Send Email To and Share actions.   Note:  For emails that are sent as HTML, the email body must be correct HTML, that is, it must start with the html element. A valid body could be created for example with the following XPath/XQuery construct: element html { element body { "Test" } }   Note: Attachments work with Android and iOS clients only. Examples •mt-email-attachment('MTNewFeatures.txt', $XML2/Releases/Release[@date='2015-04-15']/Features, 'XML') returns the Features node •mt-email-attachment('MTLogo.jpg', $XML4/Images/Image[@name='MTLogo'], 'Base64') returns an image file