Oh okay, well the link I posted in my previous comment explains that this is by design and will be like this going forward.
Administrators also have the option of converting existing email notifications to a rich HTML format (starting with the Eureka release). This format provides several advantages, including :
- Raw HTML content is converted into a WYSIWYG format.
- The content can be edited in a feature-rich HTML editor.
- Mail scripts are condensed into a single, easy-to-read line that can be reused in multiple email notifications.
- To prevent broken links, items like images and incidents, that are linked with URLs relative to a particular instance are converted to absolute links. For example, if an incident is linked using a relative URL, the link is converted to an absolute link.
| Note: The rich HTML format is the default for all new email notifications starting with the Eureka release. |
4.1 Handling Line Breaks
Rich HTML provides additional control over line breaks in your email notifications and templates. To accommodate this, a Newlines to HTML check box is available in the Email Script form to ensure that <mail_script> scripts work the same after an upgrade to Eureka.
Selecting the Newlines to HTML check box indicates that the method for handling line breaks in earlier versions carries forward for email notifications and templates used in Eureka. When an email notification or template is converted to rich HTML, the Newlines to HTML check box is automatically selected.
For new mail scripts written in Eureka, it is a best practice to add correct HTML line breaks to template.print() statements.
If an email notification or template to rich HTML is not converted to rich HTML, newlines are automatically wrapped with <div> tags, the same as versions prior to Eureka. The old mail scripts still work; however, the administrator does not enjoy the benefits of working in the rich HTML format, and does not have as much control over exact HTML formatting.
Oh okay, well the link I posted in my previous comment explains that this is by design and will be like this going forward.
Administrators also have the option of converting existing email notifications to a rich HTML format (starting with the Eureka release). This format provides several advantages, including :
- Raw HTML content is converted into a WYSIWYG format.
- The content can be edited in a feature-rich HTML editor.
- Mail scripts are condensed into a single, easy-to-read line that can be reused in multiple email notifications.
- To prevent broken links, items like images and incidents, that are linked with URLs relative to a particular instance are converted to absolute links. For example, if an incident is linked using a relative URL, the link is converted to an absolute link.
| Note: The rich HTML format is the default for all new email notifications starting with the Eureka release. |
4.1 Handling Line Breaks
Rich HTML provides additional control over line breaks in your email notifications and templates. To accommodate this, a Newlines to HTML check box is available in the Email Script form to ensure that <mail_script> scripts work the same after an upgrade to Eureka.
Selecting the Newlines to HTML check box indicates that the method for handling line breaks in earlier versions carries forward for email notifications and templates used in Eureka. When an email notification or template is converted to rich HTML, the Newlines to HTML check box is automatically selected.
For new mail scripts written in Eureka, it is a best practice to add correct HTML line breaks to template.print() statements.
If an email notification or template to rich HTML is not converted to rich HTML, newlines are automatically wrapped with <div> tags, the same as versions prior to Eureka. The old mail scripts still work; however, the administrator does not enjoy the benefits of working in the rich HTML format, and does not have as much control over exact HTML formatting.
