You can use tokens to include values from updated
fields in notification messages. You can include tokens in notification
stream messages and in the body of an email notification. You can also use a
token to create a link in an email notification message to the object record
for which the notification was generated. After a user has opened the
message, the user can click on the link to open the record in NexJ CRM.
You
can use tokens in notifications for the following subject areas:
- Business processes
- Call records
- Companies
- Contacts
- Events
- Event feedback
- Event meeting requests
- Event schedule items
- Households
- Leads
- Parent and product opportunities
- Schedule items and tasks
- Service requests
Note: If you specify an invalid token in a notification, then the
token will not be included or processed when the notification is sent.
If
the field related to the token is blank, then no value displays for the
token in notifications. The following formatting rules apply to
notifications:
- Dates and times display in medium format, followed by the time zone,
for example,
${startTimeFormatWithTimeZone} could
resolve to Jan 28, 2016 1:00 PM (EST).
- A semicolon (
;) separates multiple values that are
returned by tokens, for example,
${entityParticipantContacts} could resolve to
Bruce Tucker; Carol Welsh; Henry Collins.
Tokens for call records
The following table
lists and describes the tokens that you can use to include values from
call records.
| Token |
Description |
| ${entityFullNames} |
Contacts, companies, or households associated with a call
record |
| ${priorityStr} |
Priority of a call record |
| ${startTimeFormatWithTimeZone} |
Contact date for a call record |
| ${status} |
Status of a call record |
| ${template} |
Name of template associated with a call record |
| ${text} |
Notes for a call record |
| ${title} |
Description of a call record |
The following table lists and describes the tokens that you can
use to include links to call record objects in your email notification
messages.
| Token |
Description |
| ${url,this,title} |
Title of a call record shows as the link |
Tokens for companies
The following table lists
and describes the tokens that you can use to include values from
companies.
| Token |
Description |
| ${billToAddress fullName} |
Bill-To address for a company |
| ${businessAddress fullName} |
Default business address for a company |
| ${defaultAddress fullName} |
Preferred address for a company |
| ${defaultTelcom fullAddress} |
Preferred communication method for a company |
| ${email formattedAddress} |
Primary email address for a company |
| ${entityStatus} |
Status of a company |
| ${faxPhone fullAddress} |
Default fax number for a company |
| ${household lastName} |
Household that a company is associated with |
| ${lastName} |
Name of company |
| ${mailToAddress fullName} |
Mail-To address for a company |
| ${shipToAddress fullName} |
Ship-To address for a company |
| ${tier} |
Tier assigned to a company |
| ${workPhone fullAddress} |
Default business phone number for a company |
The following table lists and describes the tokens that you can
use to include links to company record objects in your email notification
messages.
| Token |
Description |
| ${url,this,fullName} |
Full name of a company shows as the link |
Tokens for contacts
The following table lists
and describes the tokens that you can use to include values from
contacts.
| Token |
Description |
| ${birthdaySummaryString} |
Date of birth for a contact |
| ${businessAddress fullName} |
Default business address for a contact |
| ${companyName} |
Company that a contact belongs to |
| ${defaultAddress fullName} |
Preferred address for a contact |
| ${defaultTelcom fullAddress} |
Preferred communication method for a contact |
| ${departmentName} |
Department that a contact belongs to |
| ${email fullAddress} |
Primary email address for a contact |
| ${entityStatus} |
Status of a contact |
| ${fullName} |
First and last name of a contact |
| ${homeAddress fullName} |
Default home address of a contact |
| ${homePhone fullAddress} |
Default home phone number for a contact |
| ${householdName} |
Household that a contact belongs to |
| ${position} |
Position or job title for a contact |
| ${tier} |
Tier type for a contact |
| ${workPhone fullAddress} |
Default business phone number for a contact |
The following table lists and describes the tokens that you can
use to include links to contact record objects in your email notification
messages.
| Token |
Description |
| ${url,company,fullName} |
Full name of a company shows as the link |
| ${url,household,fullName} |
Full name of a household shows as the link |
| ${url,this,firstName} |
First name of a contact shows as the link |
| ${url,this,fullName} |
Full name of a contact shows as the link |
| ${url,this,lastName} |
Last name of a contact shows as the link |
Tokens for documents
The following table lists
and describes the tokens that you can use to include values from
documents.
| Token |
Description |
| ${entityFullNames} |
Contacts, companies, or households associated with a
document |
| ${endTimeFormatWithTimeZone} |
Time and date that a document was created |
| ${priorityStr} |
Priority defined for a document |
| ${status} |
Status of a document |
| ${template} |
Name of template used for a document |
| ${text} |
Notes assigned to a document |
| ${title} |
Description of document |
The following table lists and describes the tokens that you can
use to include links to documents in your email notification
messages.
| Token |
Description |
| ${url,this,title} |
Title of a document shows as the link |
Tokens for events
The following table lists and
describes the tokens that you can use to include links to events in your
email notification messages.
| Token |
Description |
| ${url,company,title} |
Title of a company associated with an event shows as the
link |
| ${url,this,title} |
Title of an event shows as the link |
Tokens for event feedback
The following table
lists and describes the tokens that you can use to include links to event
feedback records in your email notification messages.
| Token |
Description |
| ${url,this,title} |
Title of an event feedback record shows as the
link |
Tokens for event meeting requests
The following
table lists and describes the tokens that you can use to include values
from event meeting requests.
| Token |
Description |
| ${entityParticipantCompanies} |
External company contacts assigned to an event meeting
request |
| ${entityParticipantContacts} |
External contacts assigned to an event meeting
request |
| ${leg city} |
City for the event leg associated with an event meeting
request |
| ${leg globalRegion} |
Global region for the event leg associated with an event
meeting request |
| ${leg title} |
Title of the event leg associated with an event meeting
request |
| ${meeting assignToCaption} |
Users assigned to an event meeting request |
| ${meeting endTimeFormatWithTimeZone} |
End date and time for an event meeting request |
| ${meeting sectorIndustriesCaption} |
Sectors or industries assigned to an event meeting
request |
| ${meeting startTimeFormatWithTimeZone} |
Start date and time for an event meeting request |
| ${meeting template name} |
Template name of meeting associated with an event meeting
request |
| ${meeting tickersCaption} |
Tickers assigned to an event meeting request |
| ${meeting title} |
Description of an event meeting request |
| ${roadshow category} |
Event type for an event meeting request |
| ${roadshow company fullName} |
Company names for which the event is held |
| ${roadshow title} |
Event title for an event meeting request |
| ${status} |
Status of an event meeting request |
| ${text} |
Notes for an event meeting request |
The following table lists and describes the tokens that you can
use to include links to event meeting request records in your email
notification messages.
| Token |
Description |
| ${url,this,title} |
Title of an event meeting request shows as the
link |
Tokens for event schedule items
The following
table lists and describes the tokens that you can use to include values
from event schedule items.
| Token |
Description |
| ${assignToCaption} |
Users assigned to an event schedule item |
| ${callRecord title} |
Description of a call record |
| ${entityParticipantCompanies} |
External company contacts assigned to an event schedule
item |
| ${entityParticipantContacts} |
External contacts assigned to an event schedule
item |
| ${endTimeFormatWithTimeZone} |
End date and time for an event schedule item |
| ${leg city} |
City for the event leg associated with an event schedule
item |
| ${leg globalRegion} |
Global region for the event leg associated with an event
schedule item |
| ${leg title} |
Title of the event leg associated with an event schedule
item |
| ${priorityStr} |
Priority for an event schedule item |
| ${roadshow companyNames} |
Company names for which the event is held |
| ${roadshow template} |
Event type for an event schedule items |
| ${roadshow title} |
Event title for an event schedule item |
| ${sectorIndustriesCaption} |
Sectors or industries associated with an event schedule
item |
| ${startTimeFormatWithTimeZone} |
Start date and time for an event schedule item |
| ${status} |
Status for an event schedule item |
| ${summaryHeading} |
Description of an event schedule item. The template name
if a description is not provided. |
| ${template} |
Name of the template used for an event schedule
item |
| ${text} |
Notes for an event schedule item |
| ${tickersCaption} |
Tickers associated with an event schedule item |
| ${title} |
Description for an event schedule item |
The following table lists and describes the tokens that you can
use to include links to event schedule items in your email notification
messages.
| Token |
Description |
| ${url,this,title} |
Title of an event schedule item shows as the link |
Tokens for households
The following table lists
and describes the tokens that you can use to include values from
households.
| Token |
Description |
| ${billToAddress fullName} |
Bill-To address for a household |
| ${businessAddress fullName} |
Default business address for a household |
| ${defaultAddress fullName} |
Preferred address for a household |
| ${defaultTelcom fullAddress} |
Preferred communication method for a household |
| ${email formattedAddress} |
Primary email address for a household |
| ${entityStatus} |
Status for a household |
| ${faxPhone fullAddress} |
Default fax number for a household |
| ${lastName} |
Name of a household |
| ${mailToAddress fullName} |
Mail-To address for a household |
| ${shipToAddress fullName} |
Ship-To address for a household |
| ${tier} |
Tier type for a household |
| ${workPhone fullAddress} |
Default business phone number for a household |
The following table lists and describes the tokens that you can
use to include links to households in your email notification
messages.
| Token |
Description |
| ${url,this,fullName} |
Full name of a household shows as the link |
Tokens for leads
The following table lists and
describes the tokens that you can use to include values from
leads.
| Token |
Description |
| ${companyFullName} |
Name of a company specified for a lead |
| ${fullName} |
First and last name of a person specified for a
lead |
The following table lists and describes the tokens that you can
use to include links to leads in your email notification messages.
| Token |
Description |
| ${url,person,fullName} |
Title of a related contact shows as the link |
| ${url,company,lastName} |
Related company name for a lead shows as the link |
| ${url,this,fullName} |
First and last name of a lead shows as the link |
Tokens for opportunities
The following table
lists and describes the tokens that you can use to include values from
opportunities and progressed opportunities.
| Token |
Description |
| ${title} |
Title of the opportunity |
| ${typeString} |
Type of parent or product opportunity |
The following table lists and describes the tokens that you can
use to include links to opportunities in your email notification
messages.
| Token |
Description |
| ${url,primaryEntity,fullName} |
Full name of the opportunity's associated contact shows
as the link |
| ${url,this,title} |
Title of an opportunity shows as the link |
Tokens for schedule items and tasks
The
following table lists and describes the tokens that you can use to include
values from schedule items and tasks.
| Token |
Description |
| ${assignToCaption} |
Users assigned to a schedule item or task |
| ${callRecord title} |
Description of a call record |
| ${entityParticipantCompanies} |
External company contacts assigned to a schedule item or
task |
| ${entityParticipantContacts} |
External contacts assigned to a schedule item or
task |
| ${endTimeFormatWithTimeZone} |
End date and time for a schedule item, or the due date
for a task |
| ${priorityStr} |
Priority for a schedule item or task |
| ${sectorIndustriesCaption} |
Sectors or industries associated with a schedule item or
task |
| ${startTimeFormatWithTimeZone} |
Start date and time for a schedule item, or the start
date for a task |
| ${status} |
Status of a schedule item or task |
| ${summaryHeading} |
Description of schedule item or task. The template name
if a description is not provided. |
| ${template} |
Name of the template used for a schedule item or
task |
| ${text} |
Notes added to a schedule item or task |
| ${tickersCaption} |
Tickers associated with a schedule item or task |
| ${title} |
Description of a schedule item or task. |
The following table lists and describes the tokens that you can
use to include links to schedule items or tasks in your email notification
messages.
| Token |
Description |
| ${url,this,title} |
Title of a schedule item or task shows as the
link |
Tokens for service requests
The following table
lists and describes the tokens that you can use to include values from
service requests.
| Token |
Description |
| ${assessmentValue} |
Current assessment of a service request |
| ${assignToCaption} |
Users assigned to a service request |
| ${channel} |
Communication channel used for a service request |
| ${closeComment} |
Resolution notes for a service request |
| ${closeTimeFormatWithTimeZone} |
Date and time when a service request is closed |
| ${dueTimeFormatWithTimeZone} |
Date and time when a service request must be closed based
on service level agreement rules |
| ${externalIdentifier} |
External ID associated with a service request |
| ${firstResponseDueTimeFormatWithTimeZone} |
Date and time when the first response must be sent based
on service level agreement rules |
| ${firstResponseTimeFormatWithTimeZone} |
Date and time when the first response is sent for a
service request |
| ${openTimeFormatWithTimeZone} |
Date and time when a service request is opened |
| ${primaryEntity fullName} |
Primary entity associated with a service request |
| ${priority} |
Priority of a service request |
| ${requestIdentifier} |
ID associated with a service request |
| ${severity} |
Severity of a service request |
| ${stageValue} |
Current stage of a service request |
| ${template} |
Name of the template used for a service request |
| ${text} |
Notes associated with a service request |
| ${title} |
Description for a service request |
The following table lists and describes the tokens that you can
use to include links to service requests in your email notification
messages.
| Token |
Description |
| ${url,this,title} |
Title of a service request shows as the link |
