Question:
How can a template token change without being modified by a user in Vault?
Answer:
A token can change if an imported configuration package file creates a field with the same label as a token.
Example: dueDate
- 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.
Related Documentation:
- Vault Notification Documentation: Notifications Documentation
- Vault Configuration Migration Documentation: Packages