Settings to create incidents by using email messages
This section describes the settings that you can configure to create incidents from email messages. The Incident - Email Settings option in the Configure Email tile provides these settings.
The following sections are provided on the Incident - Email Settings page:
- Creating Incidents from Client Emails--Enables you to configure settings to create incidents from an email message based on its subject and assign these incidents to a user (Context User, Queue, or Staff).
- Identifying the Email Sender--Enables you to compare the email address of a received email message to more than one field and assign the client to an incident if the email address of a received email does not match any of the client records.
- Mapping Email Content to Incident Fields--Enables you to configure mapping of the data in the email body, From email address, and Subject of the email to the fields of the Incident form.
The following table describes the options provided in each of these sections:
|Creating Incidents from Client Emails|
|Create an incident with any email subject|
Allows clients to create incidents by sending an email with any subject or create an incident if an email does not have a subject. The client must ensure that the subject line does not contain the following words:
|Create an incident only when the email subject contains|
Allows clients to create incidents by sending an email with a defined subject. This option is selected by default. Type the required subject in the text box.
When a client sends an email message to create an incident, the message subject line must contain the subject that you have defined.
|Do not create an incident when the email subject contains|
Allows system administrators to configure keywords to stop creation of incidents for email messages with a subject that contains the specified keywords.
Type the required keywords in the text box. The keywords must be separated by the ',' delimiter and can contain special characters. Ensure that there is no space after the delimiter. For example, if Re:, Close Incident, and FW: are keywords, you must write them like this - Re:,Close Incident,FW:.
Note: The Create an Incident only when the email subject contains:* and. Do not create an incident when the email subject contains fields must not contain the same values.
|Create an incident if email address is in Cc field|
Allows clients to create incidents by sending an email message where the listener email address is in the Cc field. If the listener email address is in Cc and To fields, only one incident is created related to that email message.
This option is not selected by default. If the option is not selected and the listener email address is in Cc field and not in the To field, incident is not created.
Note: This option does not apply if your organization uses email forwarding to send email messages to the email listener address. In this case, incidents are created even if you do not select this option. However, you can configure your email forwarding rule to not send an email message to BMC Remedyforce when the email address is in the Cc field.
|Assign email-generated incidents to|
The following options are provided in the list:
|User to receive email processing error notifications|
Select the user who must receive email notification when an incident cannot be created through an email message.
The email notification that is sent to the specified user contains error description and the original email message.
If no user is selected in this field, email notifications are sent to the email address that is specified in the Route Error Emails to This Email Address field. The Route Error Emails to This Email Address field is available on the Email Service page for createincident email service. To access the createincident email service, navigate to Remedyforce Administration > Configure Email > Email Services. On the Email Services page, for the createincident email service, click Edit in the Action column.
|Save the email message in Action History|
Allows you to save the email message from which an incident is created.
If this option is selected, when an incident is created by using an email message, the email message is saved as an Email Received record in the Action History section of the incident. The staff member can reply to the email message to communicate with the client.
|Identifying Email Sender|
|If an Email is from a||Select the required option from the list. The Contact and Lead options are displayed in the list if theContact and Lead options are selected in the Client Users Include section on the Manage Users > User Settings page.|
|Available Email Fields|
Select the fields with which you want to compare the email address present in the From field of the email message, and click the right arrow to move the selected fields to the Selected Email Fields list.
To remove the selected fields, select the fields in the Selected Email Fields list and click the left arrow.
Note: You cannot remove the Email field from the Selected Email Fields list. You must specify the search options for all the options available in the If an Email is from a field.
|Client for Unidentified Sender||Select the appropriate client. If no match is found while comparing the fields selected in the Selected Email Fields list with the email address present in the From field of the email, the client that you select in the Client for Unidentified Sender field is used as the client for the incident when an incident is created from the email. If the Client for Unidentified Sender field is not specified, the email message is ignored and the incident is not created.|
|Mapping Email Content to Incident Fields|
Select the appropriate delimiter.
To save data inside the email body, you need to enclose the data with a delimiter. For example, you select # as a delimiter. To get category from the email body, the category value must be enclosed in #, such as #Hardware#, in the email body.
For guidelines to map Incident form fields to keywords in the email message, see Guidelines to map email content to Incident fields.
|Include prefix in mapped fields||Select the check box to include prefixes, such as To:, From:, in the values of the incident fields that you map to an email message. For more information, see Including prefixes in mapped fields.|
|Incident Field||Select the field on the Incident form in which the data is saved.|
From the list, select the required option. The following options are provided:
|Keyword||Enter the keyword that is searched in the email message. You can specify a keyword to be searched only in the subject and body of the email message. When you specify a keyword, the word is searched in the subject or body and is copied to the mapped field instead of the entire content of the subject or body of the email message.|
|To add the mapping.|
|To remove a mapping.|
|To update a mapping.|
Guidelines to map email content to Incident fields
Ensure the following in the email message that you send to create incidents in BMC Remedyforce:
- If you have not mapped any email content, then the whole email body is saved as value in the Description field.
- You can map email content with the incident fields without entering any keyword. If you have mapped the email content to any field on the Incident form without entering any keyword, then the whole information is saved as value in the field. For example, if the Description field of the Incident form is mapped with body of the email message without any keyword, then while creating the incident, the whole email body is copied to the Description field.
- If you are using keywords, then the keyword is searched in the email message and the information is saved as value in the field. However, if you are using keywords, ensure the following points:
- There should be no text between two consecutive keyword-value pairs.
- BMC recommends that you must have keyword-value pair in different lines.
- There should be no space between the keyword and value.
- If you have mapped the email content to any field on the Incident form, then the information is saved as value in the field.
- If the mapping contains Email Message, then the whole email content is saved as value in the mapped field.
- Ensure that the Date and Date Time format in the email is yyyy-mm-dd and yyyy-mm-dd-hh-mm-ss.
- You can use the delimiter only to map email content to the Incident form fields. If you use the delimiter other than for mapping purpose, there can be errors in mapping and failure in creating incident. However, you can also create incidents without using the delimiters.
The following table describes the valid data types for mapping of email content:
Email content mapping Valid data types Sent TextArea, Text From TextArea, Text, Email To TextArea, Text Cc TextArea, Text Subject Any Data type Body Any Data type
Sample email message 1
To: email@example.com, firstname.lastname@example.org
Cc: email@example.com, firstname.lastname@example.org
Subject: Game server HDD crashed.
Game server HDD has crashed.
Game Server down. All APAC users off-line.
In this example, an incident is created by using the information from the received email message.
Sample email message 2
I need help for an issue for which the details are the following:
Description##XYZ software not installing, says abc is the problem##
In this email message, Config Item is a keyword and BS1 is the value. In this example, consider that the Config Item keyword is mapped to Configuration Item lookup field on the Incident form.
In this example, if the Subject of the email message is mapped to the Incident Description field, and Category is added as a keyword, then the value of the Incident Description field is Software.
Mapping of keywords is done on the Mapping Email Content to Incident Fields section.
Including prefixes in mapped fields
Prefixes, such as Body:, From:, and so on, are included or excluded from the mapped fields depending upon the status of the Include prefix in mapped fields check box and email content mapping with incident fields. The following table describes if the prefixes are included or not based on the field mapping and the status of the Include prefix in mapped fields check box.
|Field mapping defined||Include prefix in mapped fields check box||Prefixes included or removed|
|No||Selected||All of the email content is saved with prefixes in the Description field of the incident.|
|No||Clear||All of the email content is saved with prefixes, except the "Body:" prefix, in the Description field of the incident.|
|Yes||Selected||All data is saved with prefixes in the mapped incident fields.|
|Yes||Clear||All data is saved without prefixes in the mapped incident fields.|
|Incident fields are mapped to any email message field and Email Message||Selected||All data is saved with prefixes in the mapped fields.|
|Incident field is mapped to Email Messageonly||Clear||All data with prefixes, except the "Body:" prefix, is saved in the mapped fields.|
|Incident field is mapped to any email message field (such as, Subject) and Email Message||Clear|
The following data is saved in the mapped incident field:
Guidelines to map email content to Incident template
When you send an email message, the template can be applied to the Incident and populate the field values in that incident. For this, you must specify the template name in the beginning of, either the subject line or any line in the body of that email message. See the following use cases to map email content to the incident template:
Use case 1: If the subject line starts with the template name within delimiters:
Subject: $T##TemplateName## subject line continues
Use case 2: If the first line of the body starts with the template name within delimiters:
Body: $T##TemplateName## body continues
Use case 3: If a line in the body starts with the template name within delimiters:
Body: Body line 1
$T##TemplateName## body continues