Skip to content

All Vaults include system-provided tokens for Vault information: vault_id__sys, vault_name__sys, and vault_dns__sys. You can define and store up to ten (10) additional tokens using the Vaulttoken MDL component type or from Admin > Configuration > Vault Tokens in the Vault UI. Once configured, Vault tokens can be used anywhere in your Vault.

For example, you might create a Vault token with the name my_subdomain__c and the value "veepharm" in your production Vault. In your sandbox Vault, you create another Vault token with the same name and the value "veepharm-sbx". You can then set the URL to http://${Vault.my_subdomain__c}.veepharm.com in a Connection record, and Vault resolves the token to the correct subdomain for each Vault.

The following example MDL command creates a my_subdomain__c Vault token with a value of "veepharm-sbx":

RECREATE Vaulttoken my_subdomain__c ( label('Veepharm Sandbox'), active(true), clone_behavior('clear__sys'), type('string__sys'), system_managed(), value('veepharm-sbx') );