Setting the Target Platform for Approved Email Content
Vault CRM supports Approved Email content developed for both Veeva CRM and Vault CRM. To allow both new and existing content to function correctly in Vault CRM, content creators must set the appropriate content target platform on Approved Email content.
Existing content that includes tokens that reference Veeva CRM API Names must be set with a target platform of Salesforce. For example, {{Account.Formatted_Name_vod__c}}. Otherwise, content should be set with a target platform of Vault.
Who can use this feature?
- Browser Users
- Users require an Approved Email license
- Content Creators, End Users, Integration Users
Configuring the Content Target Platform for Approved Email Content for
Approved Email Integration Users
To configure this feature:
-
Grant Edit field permission to the target_platform__v field on the approved_document__v object.
-
Navigate to CRM Setup > Content Setup > Approved Email.
-
Update the field mapping for the appropriate PromoMats/MedComms connection to ensure the target_platform__v field in CRM is mapped to the target_platform__v field in PromoMats/MedComms.
If integration users are not configured and the target_platform__v field in CRM is set to vault__v by default for all Approved Email content, then all Approved Email content will function as developed for Vault CRM
End Users
To configure this feature, grant Read field permission to the target_platform__v field on the approved_document__v object.
Setting the Content Target Platform for Approved Email Content as
Content Creators
When creating or editing Approved Email content in PromoMats/MedComms, content creators must set the content target platform according to the API names used in the content.
Content creators should set the content target platform to Salesforce (salesforce__v) when the content includes tokens that reference Veeva CRM API Names. When content includes references to Vault CRM API Names, the target platform must be set to Vault (vault__v). If content does not include tokens with references to any API names, the target platform should be set to Vault.
For example, a template that includes the {{Account.Formatted_Name_vod__c}} token should have the target platform set to Salesforce. A template that includes the {{account__v.formatted_name__v}} token should have the target platform set to Vault.
Note: Approved Email tokens are case sensitive.
Note: In the 24R2 release, the Browser platform does not support Approved Email content that includes tokens referencing Vault CRM API Names.
The content target platform must be set on both email templates and email fragments. Email fragments are not required to have the same target platform as the template they are used in. For example, an email fragment with a target platform of Salesforce can be added to an email template with a target platform of Vault.
To set the content target for Approved Email content in PromoMats/MedComms:
-
Navigate to an Approved Document.
-
Select Edit.
- Select the appropriate value for the target_platform__v field. The following values are available:
- Salesforce (salesforce__v)
- Vault (vault__v)
If left blank, the target platform is interpreted as salesforce__v.
-
Select Save.
