Hi Neha,
Yes you can add custom fields onto an email, you need to use the following:
>SM_CUV_VariableName]
The variable name needs to match the Shortcode of the variable on your form, that variable is named as a single string - eg “ROOTCAUSE” rather than “ROOT CAUSE” or “ROOT-CAUSE”.
If you wish to email out all system fields you can use:
/SM_CUSTOM_FIELDS]
It is possible to add additional “system” variables to your variables list - by this needs to be done on your integration server, opening the Additional_Variables.lua file found within your action processor. You will need to give the variable a name and then give the path of the field you wish to add example:
e"AV_AFF_USER_EMAIL"] = "event.affectedUserEmail",
Gives us the the affected users email address. These values would be added to your action templates in the following format
mSM_AV_AFF_USER_EMAIL]
Be careful of adding too many custom variables to your additional variables file though as this can increase your outbound mail processing time significantly.
I hope this helps
Kevin
For an action template, you can use the following syntax:
For single select lookup:
$new.event.W("SHORTCODE").name
For string fields:
$new.event.W("SHORTCODE")
Not sure about other field types (boolean, multi select, date, etc).