Convert legacy email notifications to rich HTML
-
- UpdatedFeb 1, 2024
- 2 minutes to read
- Washington DC
- Notifications
By default, new email notifications are created in the rich HTML format. But you can also convert legacy notifications to rich HTML.
Before you begin
Procedure
What to do next
When you convert an email notification that was created in a version prior to Eureka to rich HTML, mail scripts are automatically moved to the Email Script [sys_script_email] table and an embedded script tag with the name of the script is automatically inserted into the body of the notification.
When creating new email notifications, write mail scripts using ${mail_script:script
name}
embedded script tag to the email notification body. This makes it
easy to use the same scripts in multiple email notifications. All you need to copy
and paste from one notification to the next is the embedded script tag.
If you manually enter a mail script, any text bounded by <mail_script>
</mail_script>
in the body of a new or converted email notification
or template which is saved to the record, a message asks whether the mail script
should be converted.

In many cases, an unconverted mail script fails to run from inside the HTML editor. If you select Yes, the script is added to the Email Script [sys_script_email] table and is automatically replaced in the body with an embedded script tag. You can view the mail scripts in their original form by opening the email notification and clicking the Show Notification Scripts related link.