Veeva Vault Bugs
A small collection of bugs present in the Veeva Vault platform.
Custom text not displaying correctly in sent email or Salesforce.
Be sure you have no customText tokens hidden in HTML comments. Veeva Vault will mess up those tokens displaying the selections incorrectly, because although they don't show, as the markup is hidden in a comment, they will still interfere with the visible ones.
Never have this in a template:
<!-- {{customText[test|test2|test3]}} -->
Email is not being sent from salesforce.
When sending an email from SalesForce to your personal email to generate a render proof, it can sometimes display the message "sent to 0 of 1 recipients". One possibility for this failure might be that the "email domain" field is set on the piece.
Check the email domain field in Veeva Vault and be sure it is empty as this limits the domains to which the email can be sent.
Fragment or template in not being recognized as an HTML Document.
A fragment or email template may never have an HTML comment on the first line of the document. If it has the piece will not be recognized as valid html. If you need an HTML comment on the beginning of the file, insert a line break before it.
Custom Text Token is not displaying on the iPad app.
When using the custom text tag there should be no space between the closing square bracket and the closing curly brace.
If there is a space in that location the email template will work fine on the salesforce website but it will fail on the Veeva iPad app.
It should be like this:
{{customText[test|test2|test3]}}
It will fail on the iPad like this:
{{customText[test|test2|test3] }}
Language defaults to English when making a copy of an existing document
When making a copy of an existent piece and you choose the "copy fields" option, the language field will always be set to English US. Please keep this in mind when copying pieces and change the language to the correct one.
Link error
Never use a <p> tag inside an <a>. Veeva will break the code and the link will not work.