Share:

PREVIOUS  |  NEXT

Email Template Tags

Quick Links


Notice: We are currently working to improve this content. Once revisions are finalized, we will add the article to the Recently Updated Articles section on the product's Documentation Home page. Learn more.


Global

[Back to top] 

Tag Description
$!{performer}  Related case name
$!{ project.name URL of current case
$!{oldProjectName}  Previous case key, if it was changed. See 'Project change' email template in prastova@calliduscloud.com to see how this can be used.   
$!{case.description}  Case description
$!{case.caseKey}  Case key. 
$!{case.status.name}  Current status of related case
$!{case.project.name}  Project related to case 
$!{case.priority.name}  Case priority 
$!{case.priority.position  Position in the priority array of the related case. 0 is the highest priority. See Priority Field for more information.
$!{case.assigneeName}  Name of the user assigned to the case
$!{case.createdBy.userName}  Full name of the user to who created the case
$!{case.createdBy.firstName}  First name of the user to who created the case
$!{case.createdBy.lastName}  Last name of the user to who created the case
$!{case.createdBy.email}  Email of the user to who created the case
$!{case.owner.userName}  Name of the user to who is the case owner
$!{barcode.linkImg}  Barcode image generated for current case key
Tag Description
$!{performer}  Related case name
$!{ project.name URL of current case
$!{oldProjectName}   
$!{case.description}  Case description
$!{case.caseKey}  Case key. 
$!{case.status.name}  Current status of related case
$!{case.project.name}  Project related to case 
$!{case.priority.name}  Case priority 
$!{case.priority.position  Position in the priority array of the related case. 0 is the highest priority. See Priority Field for more information.
$!{case.assigneeName}  Name of the user assigned to the case
$!{case.createdBy.userName}  Full name of the user to who created the case
$!{case.createdBy.firstName}  First name of the user to who created the case
$!{case.createdBy.lastName}  Last name of the user to who created the case
$!{case.createdBy.email}  Email of the user to who created the case
$!{case.owner.userName}  Name of the user to who is the case owner
$!{barcode.linkImg}  Barcode image generated for current case key
Tag Description
$!{performer}  Related case name
$!{ project.name URL of current case
$!{oldProjectName}   
$!{case.description}  Case description
$!{case.caseKey}  Case key. 
$!{case.status.name}  Current status of related case
$!{case.project.name}  Project related to case 
$!{case.priority.name}  Case priority 
$!{case.priority.position  Position in the priority array of the related case. 0 is the highest priority. See Priority Field for more information.
$!{case.assigneeName}  Name of the user assigned to the case
$!{case.createdBy.userName}  Full name of the user to who created the case
$!{case.createdBy.firstName}  First name of the user to who created the case
$!{case.createdBy.lastName}  Last name of the user to who created the case
$!{case.createdBy.email}  Email of the user to who created the case
$!{case.owner.userName}  Name of the user to who is the case owner
$!{barcode.linkImg}  Barcode image generated for current case key
Tag Description
$!{performer}  Name of the user who performed the action.
$!{project.name Name of the current project.
$!{oldProjectName}  Previous case key, if it was changed. See changeProject system email template to see how you can use this tag. 
$!{action.name}  Name of the action for which we will send the notification. 
$!{domain}  Name of the tenant. 
$!{appUrl}  Workflow application URL.
$!{subjectPrefix}  The email notification subject prefix that you can configure in Setup > System Settings > Email Settings, in the Default Email Prefix field. See Email Settings for more information.
$!{caseLink}  Link to the current case. 
$!{hasReplyToAddress}  If this is true, recipient can post a new comment by simply replying to this email. This will be true if you enable the E mail to Case feature. See Email to Case Rules for more information.
$!{replyCode} 
$!{message}  Displays the content of the message that a user enters. You can use this tag in the Share Case and Send Message actions. For the Delete Case action, this tag contains the message that users can enter as a reason for deleting a case. 
$!{performerProfile}  Link to the user's profile in the workflow.
$!{recipient} 
$!{reminder.name}   Name of the ad-hoc reminder. You can use this tag only in the reminder system email template. 
$!{reminder.createdBy.userName}  Name of the person who created the ad-hoc reminder. You can use this tag only in the reminder system email template. 
$!{reminder.createdOn} Date and time when the ad-hoc reminder was created. You can use this tag only in the  reminder system email template. 
$!{daysPassed}
$!{barcode}
$!{contextPath} 
$!{translator Use as a $translator.get("dictionary.key") tag, where dictionary.key is a message key from a specific user-defined dictionary. For more information, see Translations.
$!{customParam} 
$!{companyName} Name of the company that you defined in the Setup > System Settings > Organization Settings. Works for any action type, in both system and custom email templates. 
$!{companyAddress}Address of the company that you defined in the Setup > System Settings > Organization Settings. Works for any action type, in both system and custom email templates. 
$!{companyDescription} Description of the company that you defined in the Setup > System Settings > Organization Settings . Works for any action type, in both system and custom email templates. 


Case-Related Data

[Back to top]

Tag Description
$!{case.name}  Related case name. Works for any action type, in both system and custom email templates.
$!{case.safeName}  If a case name doesn't exist, it returns the case key; otherwise, it returns the case name. This works for any action type, in both system and custom email templates. 
$!{case.description}  Case description. Works in any action type, and in both system and custom email templates. 
$!{case.caseKey}  Case key. Works in any action type, and in both system and custom email templates. 
$!{case.caseType.name} Name of the workflow. Works in any action type, and in both system and custom email templates. See the changeCaseType system email template for an example of how to use this tag. 
$!{case.status.name} 

Current status of a related case. Works in any action type, and in both system and custom email templates.  

$!{case.assigneeName}  Name of the user to whom the case is assigned. This tag works with any action type, and in both system and custom email templates.  
$!{case.createdPerson.name}  Name of the person who created the case. This tag works with any action type, and in both system and custom email templates.  
$!{case.contact}  Contact's name. This tag works with any action type, and in both system and custom email templates.  
$!{case.account}  Account's name. This tag works with any action type, and in both system and custom email templates.  
$!{caseHistory }Reference to entire case history. See caseHistory system email template for an example of how to use this tag. 
$!{nextAssignee}  Name of the user to whom the case will be assigned. This tag only works with actions that change the assignee. See the reopenCase system email template for an example of how to use this tag.
$!{allAssignees}  Names of all users to whom the case was assigned before. This tag works with any action type in both system and custom email templates. See the  assignCase and caseDetails system email template for an example of how to use this tag.  
$!{fileName}  Name of the file that has been attached, if any. This tag only works with the Attach file action type. See attachFile and deleteAttachment system email template for an example of how to use this tag.  
$!{htmlFileName} Name of the attached file. This tag only works with the Attach File action type. See the attachFile system email template for an example of how to use this tag.
$!{downloadLink}  Link for downloading attached files. This link will only work for registered users when they login to the application, and only works with the  Attach File action type. See the attachFile system email template for an example of how to use this tag. 
$!{revisionFileName}  Name of the revised file. This tag only works with the Attach File action type. See the attachFile system email template for an example of how to use this tag .
$!{replaceFileName}   Name of the file that was replaced. This tag only works with the Attach File action type. See the attachFile system email template for an example of how to use this tag.
$!{fileSize}   Size of the file. This tag only works with the Attach File action type. See the attachFile system email template for an example of how to use this tag.
$!{comment} Comment text that was entered in the action. This tag works with actions that can add comments.
$!{commentInternal}  Identifies if the comment internal or not. This tag works with actions that can add comments. 
$!{ commentEntity

In system email templates that display comments on an action , Workflow displays the following links:

  • Add Comment:  Click on the link to be redirected to the case, and the  Add Comment action will open. 
  • Reply: Click on the link to be redirected to the case, and the Reply window for that particular comment will open. 
  • View Thread: Click on the link to be redirected to the case,  and scrolled down to that comment thread. 
$!{commentHistory}  Reference to the entire history of case comments. This tag works with actions that add comments. See the commentCase, commentHistory, deleteComment, updateComment system email templates for an example of how to use this tag.   
$!{oldCaseKey} Previous case key, if it was changed. This tag works with actions that change the case key, such as  Change Project and Change Workflow action types.
$!{oldCaseName} Previous case name, if it was changed. This tag only works with the  Merge Cases action type. See the mergeCases system email template for an example of how to use this tag. 
$!{oldCaseType}
Previous case key, if it was changed. This tag works with the  Change Workflow action type.  See the changeCaseType  system email template for an example of how to use this tag.
$!{oldStatus}   Previous case status. This tag works with any action that changes the case status. See the changeStatus system email template for an example of how to use this tag. 
$!{stopWatchingLink}  Click on the link to remove the recipient from the list of case followers. This tag works with any action type and the tag is included in the footer system email template.
$!{isWatcher}  Check if the recipient is following the case or not. This only works with the stopWatchingCase and watchCase system email templates.
$!{updatedAttributes} 

Lists standard fields that were updated on the action and includes the following information: 

  • Standard field name
  • New value
  • Old value
$!{updatedCustomFields}  Lists custom fields that were updated on the action and includes the following information:
  • Custom field name
  • New value
  • Old value
$!{waitingUsers}  Displays all users for which the case is awaiting approval. This tag works only in Custom Multi User Action and Multi User Approval action type. See  join action and multi approve system email templates to see how you can use this tag.   
$!{operationName}   Displays if the case approved or not. This tag only works with the Custom Multi User Action and Multi User Approval action types. See the join action and multi approve system email templates for examples of how to use this tag. 
$!{conditionFulfilled}  Checks whether the condition is true or false. This tag only works with the  Custom Multi User Action and Multi User Approval action types. See the join action and multi approve system email templates for examples of how to use this tag.   
$!{case.ipdatedOn}The date on which the case was last updated.


Case-Related Custom Fields

Tag Description
$!{case.getValue(" customFieldName" )}

Display any custom field on a case by entering the custom field name in place of customFieldName. To find the name of the desired custom field, go to Setup > Fields & Forms > Custom Fields.


Note: In most Workflow processes, you will use the system ID value for calling objects. When using tags to get a value for custom fields and container objects in document templates, you will use the object name instead of the system ID.


Related to Guest Users

Tag Description 
$!{isGuest}  Returns if the recipient is a guest user or not.  See the attachFile system email template for an example of how to use this tag. 
$!{guestViewCaseLink}  Renders a link to view a guest case. See the caseKey system email template for an example of how to use this tag.  
$!{guestUnregisterLink}  Renders a link by which a user can unregister as a guest on a case.  This tag is included in the footer system email template. 
$!{guestLink}


User-Related

[Back to top]

Tag Description 
$!{user.userName}   Name of the user. This tag only works with system email templates when a user is created, added to a case team, or in password changing emails. 
$!{changePasswordLink}  Renders a link by which a user can change the password. See passwordChangeRequest  system email template for an example of how to use this tag.
 $!{userPassword}  Password of a user. This is only available when creating a user as this is the only time the user's password is available. After a user is saved to the database, the password is encrypted and can't be retrieved. This tag only works with the
passwordChangeSuccess and  userCreated system email templates.
 $!{userType} Displays the recipient's user type. This tag works with any action type. See the  newUser and  userCreated2Admin system  email templates for examples of how to use this tag.