Sending messages related to records
In BMC Helix ITSM, you can send messages related to records from the change module.
To send an email message
- Open the change request.
- Click Email
and change the request ID.
The ticket title is automatically populated in the Subject field. - In the To field, you can specify the name, login ID, email address, or corporate ID to search for a recipient. who has a profile in BMC Helix ITSM.
For people who do not have a profile in BMC Helix ITSM, enter their email addresses. In the To field, press the ↓ key to see the suggestions for email recipients. - In the compose window, enter the email details.
- Click Attach file to attach files to the email.
- Click Send.
The email is sent and the activity area displays the details of the email sent.
Track emails in the Activity feed and the Updates feed
The Activity feed and Updates feed help you get details about emails sent from a ticket. When the system successfully delivers the email, BMC Helix ITSM adds a feed about the email to the Activity feed of the ticket and the Updates feed of the followers of that ticket. You can search for emails in filters available in the Activity feed and Updates feed.
A link to the knowledge article that you emailed is available in the Activity and Updates feed. You can click the link to view the complete article.
The Activity feed displays the name of the person who sent the email, the number of recipients, and attachment, if any. You can select the number of recipients to see their name. You can select the name to view the profile. If the recipient is not registered with BMC Helix ITSM, when you click the recipient's name, an email window with the email address of the person populated in the To field is displayed.
Track emails in the Email status form
When you send an email with a file or a knowledge article attached to it, you can view the email delivery in the NTE:Notifier log form and the AR System Email Messages form in Mid Tier .
You can track the status of sent emails and PDF conversion of the article in the RKM:SHR_RKM_Document_Email_Status form in BMC Helix ITSM . To find out the status of the email, enter details of the email such as the incident ID, knowledge article ID, email subject, or the date of sending the email:
The form maintains a record of the email that the system failed to deliver. The following reasons could lead to failure in email delivery:
- The email server or the Smart IT server is down.
- The attached file is corrupt.
- The file size is more than the set limits.
- The file type is not supported in Smart ITor BMC Helix ITSM.
- Invalid email addresses of the recipients.
- Issues in PDF conversion.
Based on the reason given in the form, you may rectify the error and resend the email.
Updating filters while updating out-of-the-box email template
If you copy and rename an out-of-the-box template, you need to update the run-if qualification of the filters for the new template name, so that the Source ID gets associated correctly for the new template. For example, if you rename ITSM_Generic_Template and it has a run-if qualification ('EmailTemplateName' = "ITSM_Generic_Template"), you need to update the following filters:
- NTE:NTS:Email_SystemNT_with_EmailTemplateSetIncidentType
- NTE:NTS:Email_SystemNT_with_EmailTemplateSetProblemType
- NTE:NTS:Email_SystemNT_with_EmailTemplateSetReleaseApprovalType
- NTE:NTS:Email_SystemNT_with_EmailTemplateSetChangeApprovalType
- NTE:NTS:Email_SystemNT_with_EmailTemplateSetActivityType
- NTE:NTS:Email_SystemNT_with_EmailTemplateSetReleaseType
- NTE:NTS:Email_SystemNT_with_EmailTemplateSetKnownErrorType
- NTE:NTS:Email_SystemNT_with_EmailTemplateSetWorkOrderType
- NTE:NTS:Email_SystemNT_with_EmailTemplateSetChangeType
- NTE:NTS:Email_SystemNT_with_EmailTemplateSetRequestType
- NTE:NTS:Email_SystemNT_with_EmailTemplateSetTaskType
Instructions for classic interfaces