Skip to main content
hamburger menu Created with Sketch.
We are currently experiencing intermittent service disruption with our ticket management system. We are monitoring the situation closely and appreciate your patience while a resolution is investigated.

Search the Knowledge Base

Which Approved Email Configuration Tokens are Supported in Email Templates and Email Fragments in Veeva CRM?

  • Updated

Overview:

Which Approved Email Configuration Tokens are supported in Email Templates and Email Fragments in Veeva CRM?

Answer:

Every documented Veeva Approved Email token is supported in Email Templates. They can be used in the BODY tag of the Email Template HTML code without any restrictions.

However, in Email Fragments, Approved Email tokens are only supported inside of an href HTML tag. These include:

  • Standard tokens such as {{parentCallDatetime}}, {{userName}}, {{accFname}}
  • Tokens which are in the format of ObjectAPIName.FieldAPIName.

Example:

In the event the token {{Call2_vod__c.Veeva_Remote_Meeting_Id_vod__c}} is not placed inside of an an href HTML tag in the Email Fragment. It is not supported.

  • Tokens which require the input of the end-user are not supported.

Example:

{{Account.Id}} is supported but {{customText(255)}} is not. These tokens also have to be inside of an href HTML tag in Email Fragments.

Note: If an Approved Email token is used in a way that is not supported, it can result in an unexpected behavior. This includes the Preview or Edit modes of the Sent Email page in the online Veeva CRM functionality and also in the offline Veeva CRM application. The resulting value of the token in the received email might also be unexpected.

Related Documentation:

CRM Documentation: Approved Email Configuration Tokens

Send us your feedback: We're always looking for advice to help improve our Knowledge Base! Please let us know if this article was helpful or provide feedback on how we can improve your experience here.

Powered by Zendesk