Testing a Stationery Layout

Document created by user.oxriBaJeN4 Employee on Sep 9, 2015Last modified by user.oxriBaJeN4 Employee on Aug 25, 2016
Version 4Show Document
  • View in full screen mode

Prior to stationery being associated with a policy and applied to emails it is recommended each new version of stationery is tested. Ideally also the stationery should be viewed on different devices (e.g. computer, tablet and phone) to ensure that is viewable and the information does not get lost or corrupted.

 

The Mimecast solution has a simple means to test stationery prior to it being deployed with a policy. This is done using the Short Code which is defined the layout page. The Short Code is a unique text string that is used to identify a specific Layout.  This code can be used to manually override existing Stationery Policies and force Mimecast to apply a specific Stationery Layout. Each Stationery Layout, regardless of its location in any folder, must have a completely unique Short Code. This can be useful in a testing environment, or even for specific groups of users that are given control over which Layouts should be applied to their emails.

 

For example, multiple Stationery Layouts may be created for different products or services offered by an organization.  The Administrator will provide a Short Code listing of these different Stationery items to specific users, such as the Sales Department, so that the Sales team can target product-related Stationery Layouts to individual customers.

 

The Short Code is activated in the email Subject line, by initiating the Subject with an HTML tag ( <ins> ) containing the Short Code. This HTML tag is then followed by the actual Subject line of the email. When Mimecast processes the email,  the HTML tag itself is removed, which leaves the remainder of the Subject line intact. For example:

<ins productastationery>More information on Product A

<ins cs-amalficoast>Case Study as requested

 

If the short code matches a specific layout then the stationery policies will be ignored and the layout with the relevant short code will be applied.

 

Also, if a user needs to send an email that has no Stationery Layout at all, then the<no ins> HTML tag can be used in the Subject line of the email.  This excludes all Stationery Layouts for the email. Again, this HTML tag is followed by the real subject of the email, as the tag is automatically removed by Mimecast.

 

As major part of the testing should be to ensure that the signature can be seen on different devices such as computer, tablet and mobile phone. The test should also consider how the signature is rendered on Android and iOS devices in case there are issues.

Short Codes are designed for testing of Signatures. When sending emails they may be used to initiate specific stationery layouts if the MfO plugin is not available. They are not supported for any other purposes.  

Attachments

    Outcomes