Within email templates of the type Lightning Proposal E-mail and Lightning link proposal email we already have the option to use the merge fields special.candidateCards and special.candidateTable as part of the lightning proposal wizard.
In version 21 we have added the option to customize these merge fields per template. Use of it is optional, no mergepart has any data it will still use the old version of the merge field.
Note: using this option requires good knowledge of both HTML, CSS and more importantly the limitations of mail clients used by the receiver of the email ! ( Premium tools exist to help with the latter part, e.g. litmus.com )
Customizing a merge field
To customize these merge fields go the email template you want to change.
Connexys Setup > Email templates > Lightning Proposal E-mail / Lightning link proposal email
Below the template you can see the + that allows you to reveal the merge parts.
The mergeparts contain HTML, but also mergefields and other mergeparts.
Mergeparts will be replaced by the code on runtime, in some cases it will repeat the containing code multiple times based on e.g. the amount of candidates, fields or documents.
The mergeparts will assume that base structure remains the same (e.g. special.candidateTable will assume a table structure), deferring from this might lead to unexpected results. There for it is safest to start with the example code below and change/style from there.
Below the mergeparts is a preview containing some dummy data to give an indication how the resulting mergefield will look.
Please do keep in mind that if your preview looks good in a browser, the result may still look very different in the different mail clients ! There it is safest to use "ancient" html and inline styling only.
Mergefields for candidate data
Both candidateCards and CandidateTable accept the following mergefields.
| MergeField | Allowed in mergePart | Value |
| {!candidateLink} | mfCandidate, mfFirstField, mfTD, mfRepeatField | Field value with a link to the proposal portal of the current candidate. If there is no link available it will contain just the value of the field. |
| {!fieldName} | mfFirstField, mfRepeatField, mfTHFirst, mfTH | The label of the field |
| {!candidateValue} | mfFirstField, mfRepeatField, mfTHFirst, mfTH | The value of the field for the current candidate |
| {!documentLabel} | mfDocuments (cards only), mfDocumentField | The custom label OpenProposal_tableDocuments |
| {!mailIconUrl} | mfDocuments | A public link to the static resource mailDocumentIcon. (site url comes from application settings) |
| {!documentURL} | mfDocuments | A public link to the document |
| {!documentType} | mfDocuments | The type of the document (e.g. CV, Letter) |
All the mergeparts available on candidateCards (with an example)
| special.candidateCards | The mergefield as used on the email template |
mfCandidate |
|
| mfCandidate | Repeating mergepart that will contain the below code for each candidate available |
<table cellspacing="10" cellpadding="0" style="background-color:#f4f6f9;width:590px"> |
|
| mfFirstField | Non-repeating mergepart used for the first of the available fields |
<tr> |
|
| mfRepeatField | Repeating mergepart that will contain the below code for each field |
<tr> |
|
| mfDocumentField | Non-repeating mergepart that contains all the documents (hidden if no documents available) |
<tr> |
|
| mfDocuments | Repeating mergepart that will contain the below code for each document |
<div> |
|
All the mergeparts available on candidateTable (with an example)
| special.candidateTable | The mergefield as used on the email template |
<table style="background-color:#f4f6f9;width:600px" cellspacing="0" cellpadding="5"> |
|
| mfCandidate | Repeating mergepart that will contain the below code for each candidate available |
mfRowSeperator |
|
| mfRowSeperator | A mergepart without any mergefields that can be used as a seperator between candidates |
<tr> |
|
| mfTHFirst | Non-repeating mergepart used for the first header of the available fields |
<th colspan="1" rowspan="1" valign="top" style="text-align:left;color:#54698d;font-weight:normal"> |
|
| mfTH | Repeating mergepart containing the table header for each field |
<th colspan="1" rowspan="1" valign="top" style="text-align:left;color:#54698d;font-weight:normal"> |
|
| mfDocumentTH | Non-repeating mergepart containing the table header for the document column |
<th colspan="1" rowspan="1" valign="top" style="text-align:left;color:#54698d;font-weight:normal"> |
|
| mfTD | Repeating mergepart containing the value for each field |
<td colspan="1" rowspan="1" valign="top" style="color:#54698d"> |
|
| mfDocuments | Repeating mergepart containing the available documents |
<div> |
|
When I use this template, is it possible to enter a no-reply emailddres?
Somewere in what of the parts in the template!
The replyTo address is not part of the special.candidateTable or special.candidateCards, as these are just part of the content of the email being sent.
In fact email templates such as Lightning Proposal E-mail and Lightning link proposal email are only about configuring the content in the email.