Merge fields

A merge field is a type of placeholder used to specify where Pathway data should be inserted into a message subject or body at the time of sending. This field's boundaries are delimited by {{ and }}. Within these delimiters, the field type MERGEFIELD is specified, followed by a colon and the field name. For example, {{ MERGEFIELD: Doc_Addressee_SalCon }} in the subject text of an email template.

You can specify a merge field code manually into the relevant email template field. You can also specify a merge field code automatically by right-clicking the form and selecting from a list of available fields. In the latter case, the merge field code is inserted at the current insertion point, replacing any selected text in the process. The fields available vary depending on the context. For email templates associated with a merge type, the available merge fields correspond directly to the merge type’s available extract fields. When you right-click the list of available fields and the list is too long, move the pointer over the list by specifying the first character of the field name.

When a message based on the template is sent, everything between and including the delimiters is replaced by the Pathway data corresponding to the named field. When the field lies within an HTML message body, any special characters within the Pathway data are converted into their equivalent HTML character entities. For example, a < sign is converted to the entity &lt;. Carriage returns in Pathway data are also converted to <br> tags to provide a HTML line break.

Note: Incorrectly specified merge fields are ignored and considered part of the message text. For example, merge fields with invalid code syntax are ignored. Merge fields with an unknown field name return a value of *** Unknown field: field_name ***. If, for some reason, you are required to insert {{ combination in message text without having it considered a field boundary marker, then use {{{. This combination is converted to {{ in the final message text.