How can a template token change without being modified by a user in Vault?
A token can change if an imported configuration package file creates a field with the same label as a token.
- Prior to the VPK import, there is no document field with the attribute key dueDate. Given this, the User Interface(UI) just displays the attribute key for the token.
- After the VPK import, there is a document field with the attribute key dueDate. When displaying in the UI, the field is mapped from attribute key to public key resulting in the display of test1_due_date__c.
The user can import the field with a different label than Due Date and change the label after creation without affecting the notification.
- Vault Notification Documentation: Notifications Documentation
- Vault Configuration Migration Documentation: Packages
Send us your feedback: We are always looking for feedback to help improve our Knowledge Base! Please let us know if this article is helpful or provide feedback on how we can improve your experience by clicking here.