Receipt Property Variables

Receipt property variables are a special set of property variables that apply only when a ticket request is created using an inbound alert or email using Incoming Email and Alarm Settings. They can be:

• Tested using the Test Property Value of the Receipt in Ticket Request Mapping.
• Embedded in Message Templates when bracketed using [$ and $] notation. The message template must be referenced by a Ticket Request De-Dup and Ticket Request Mapping service procedures.
• Embedded in the edit fields of other Ticket Request De-Dup and Ticket Request Mapping service procedure commands. These are the only two service procedures that can use them.

Note: See Working with Variables for an overview of variables in service desk procedures.

Note: See Standard and Custom Property Variables for a list of standard property variables.

Note: See the Readers tab for an explanation of how tilda (~) commands are used in the subject or body of an inbound email to set the value of a ticket or note. Some of these tilda (~) commands can set the value of the receipt property variables listed here.

• [$Assignee$] - The VSA user currently assigned to the ticket.
• [$Body$] - The body text of the email or alert.
• [$Category$] - The category assigned to the ticket.
• [$Hidden$] - Always false for ticket requests creating a new ticket. When replying to an outbound ticket, including a ~hide string in the subject or body of the reply email will causes the reply message to be converted into a hidden note.
• [$ID$] - The unique ID of the ticket request. Not intended for use in procedures.
• [$IsTicketRequest$] - True if created by a system event instead of by an inbound email.
• [$Machine$] - The machine ID associated with this ticket.
• [$MachineGroup$] - The machine group of the machine ID associated with the ticket.
• [$Organization$] - The organization ID assigned to the ticket.
• [$PartitionID$] - The partition the ticket request was directed to. Not intended for use in procedures.
• [$Priority$] - The priority assigned to the ticket.
• [$ServiceDesk$] - The service desk used to create the ticket.
• [$Severity$] - The severity assigned to the ticket.
• [$SolutionType$] - The resolution of the ticket.
• For the following property variables see Test Property Value of the Receipt in Ticket Request Mapping.
  • [$SourceTag1$]
  • [$SourceTag2$]
  • [$SourceTag3$]
  • [$SourceType$]
  • [$SourceValue1$]
  • [$SourceValue2$]
  • [$SourceValue3$]
• [$Staff$] - Displays as the Contact field in the ticket editor. A contact is a staff member of an organization.
• [$Status$] - The status assigned to the ticket.
• [$SubCategory$] - The subcategory assigned to the ticket.
• [$Subject$] - The subject line of the email or alert.
• [$SubmitterEmail$] - The email address of the submitter.
• [$SubmitterName$] - The name of the person submitting the ticket. Usually this is the name of the user calling or emailing about a service issue.
• [$SubmitterPhone$] - The submitter's phone number.
• [$TargetEmailAddr$] - The email address the inbound email was addressed to.

Topic 10132: Send Feedback. Download a PDF of this online book from the first topic in the table of contents. Print this topic.