eHTML support

EngageOne™ supports the delivery of documents composed with the eHTML device. This device is supported in the following delivery channels:

• Archive delivery in batch mode.
• Email delivery in immediate mode. Additionally, you can:
  • Specify that the composed HTML will be sent as the body of email messages so that these messages can be produced and sent with HTML rich text format.
  • Specify that the composed HTML will be sent as an attachment so that email bodies can follow the original text body format provided by EngageOne™.
  • Create a custom email implementation that delivers EngageOne™-composed HTML rich text.
• FAX delivery in immediate mode.
• Print delivery for immediate and batch modes.

To define a delivery channel to use an eHTML device, enable the device for EngageOne™ Designer. Thereafter, when you import a new template or import the device, it is available in the Delivery Channels tab.

Here is an example of the two email options:

Template contains the email body

Template provides the attachment

If the template contains an image, the associated eHTML driver returns the output file in ZIP format. This is a default behavior, and can be changed by modifying the ehtml.output.zip.image.files parameter in the config-settings.xml file.

The default setting for this section is presented in the example below:

<setting>
<key>ehtml.output.zip.image.files</key>
 <value>true</value>
</setting>

If an HTML only response is required, this setting needs to be set to false. If necessary, the setting has to be modified independently for both immediate and batch delivery channels.

For immediate delivery channels, it is necessary to modify the setting in the config-settings.xml file present in:

<EngageOneInstallPath>\composition\conf\config-settings

It is recommended that the composition service be restarted if this setting is modified.

For batch delivery channels, the parameter should be modified in the config-settings.xml file present in:

<EngageOneInstallPath>\batch\conf\config-settings