Search Engine: Elastic

Article ID: 124828, created on Mar 12, 2015, last review on Mar 12, 2015

  • Applies to:
  • Business Automation


In some notification templates the placeholders are not substituted with the expected values. Examples:

  • service parameter placeholder empty in the order notification template,
  • placeholders related to subscription (e.g. expiration day) in the account notification,
  • etc


The placeholders usage depends on the notification template type.

Each message type (Account Notification, ARDoc Notification, Credit Card Notification, Subscription Notification) has set of placeholders that can be used in notification templates based on this message type. You can view list of available placeholders when you view or edit notification template (at the bottom of the screen there is section "Placeholders" with the list of available placeholders).

This limitation is logical (for example for account notifications: account can have 10 different domain subscription and in this case it is uncertain which of account's domains should replace @@Domain_FullDomainName@) and is described in documentation:


Use placeholders that are available for particular message type or create a new notification template of appropriate type to use a required placeholder.

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF