This documentation applies to the 8.1 version of Remedy IT Service Management Suite, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

System Events and Message Catalog for the Notification Engine

The System Events and Message Catalog contains all valid notification event definitions available in the notification subsystem. The following primary forms make up this catalog:

NTE:SYS-Define NT Events form

Notification events are defined in the NTE:SYS-Define NT Events form and are specific to a BMC Remedy ITSM module (Incident, Problem, Change, Request, Purchase Requisition, Asset, and so on). Notification events are primarily configured for internal support staff notifications that are sent according to the system default preferences, unless you have created your own entry for those events in the NTE:CFG-Notification Events form.

Note

 User-defined events take precedence over system-defined events.

Warning

Remember that all customer notifications are sent by email. You cannot change this setting without customization to the Notification Engine settings. If you install patches or later versions of the BMC Remedy IT Service Management, back up your work so that it is not overwritten by the installer. This warning applies to all customizations that you make to the Notification Engine.

The following table describes the fields that are provided on the NTE:SYS-Define NT Events form.

FieldDescription
Module NameSpecifies the BMC Remedy ITSM Suite module in which the notification message is used.
Notification EventSpecifies the event that triggers the notification.
Support Staff Event

Indicates whether the notification event is intended for customers or support staff.

When the Support Staff Event field is set to Yes, a corresponding record in the NTE:CFG-Notification Events form must specify the default preferences for this notification event.

DescriptionProvides a description of the notification event.
Check boxes

Select the applications or components to which the notification event is applicable.

Note: Because Problem Management is a process internal to the support organization, the Problem Management module has no customer notification events.

Notification events are defined in the NTE:SYS-Define NT Events form and are specific to a BMC Remedy ITSM module (Incident, Problem, Change, Request, Purchase Requisition, Asset, and so on). Notification events are primarily configured for internal support staff notification, which is indicated by the Yes flag in the Support Staff Event field.

When the Support Staff Event field is set to Yes, a corresponding record in the NTE:CFG-Notification Events form must specify the default preferences for this notification event

The notification is sent according to the system default preferences, unless you have created your own entry for this event in NTE:CFG-Notification Events.

Note

 User-defined events take precedence over system-defined events.

You can also use notification events for email notifications to customers who might not have a login ID or access to the application. To use notification events this way, set the Support Staff Event field to No.

Warning

Remember that all customer notifications are sent by email. You cannot change this setting without customization to the Notification Engine settings. If you install patches or later versions of the BMC Remedy IT Service Management, back up your work so that it is not overwritten by the installer. This warning applies to all customizations that you make to the Notification Engine.

Note

Because Problem Management is a process internal to the support organization, the Problem Management module has no customer notification events.

NTE:CFG-Notification Events form

The NTE:CFG-Notification Events form stores all system-wide and user-specific preferences for predefined internal (support staff) notification events. Preferences defined here include the notification method (email or alert), whether a pager notification is sent, business hour usage, holiday usage, and whether the message is a group or individual notification.

 Additional application preferences are also available, such as including priority for Incident Management and Problem Management, or Timing for a Change type notification.

SYS:Notification Messages form

The SYS:Notification Messages form contains the notification text for each event. The following table lists the fields on the form that you can use to configure and customize notification messages.

Note

In the table, fields that are marked with an asterisk (*) have an unlabeled drop-down menu on their right side. These menus provide text variables that can be inserted in the fields. For example, #Incident Number#. The standard filter workflow detects the variable and replaces it with the actual incident ticket number.

FieldDescription
Mapping section
Notification Message TagIdentifies the specific message to be sent. Must have a unique value.

You can associate each notification event with several notification messages for different companies and locales. 
LocaleSpecifies the locale in which the notification message is used. Must have a unique value.
CompanySpecifies the company for which the notification message is used. Must have a unique value.
Module NameSpecifies the BMC Remedy ITSM Suite module in which the notification message is used.
Support Staff EventIndicates whether the notification message is intended for customers or support staff.

Note: the notification workflow does not use this setting to determine which notification preferences to use when sending the notification. The actual filters supporting the notification determine whether the notification preferences are hard-coded (for example, always using email as the notification method, as with customer notifications) or retrieved from the NTE:CFG-Notification Events form (for example, use the system default or user-defined notification method specified for the recipient, as with support staff notifications).
Notification EventSpecifies the event that triggers the notification.
Form NameSpecifies the form in which the trigger event occurs.
DescriptionProvides a description of the notification mapping.
Other fields
Pager Message Alpha*Specifies the text that is sent to an alphanumeric pager.
Notification TextSpecifies the text of the notification message that is displayed on-screen.
Email Subject Line*Specifies the Subject line of the notification message that is sent by email.
Email Message Body*Specifies the text of notification message that is sent by email.
Email Template Name*Used in the Email Based Approval feature. This field specifies the primary template that is used to send approval notifications by email.
Fallback Template Name*Used in the Email Based Approval feature. This field specifies the secondary template that is used to send approval notifications by email, if the primary template is unavailable.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments

  1. Stefan Hall

    Hi,

    the explanation for "Fallback Template Name" seems not complete. The fallback template will be used too if the approval process needs a justification.

    Stefan

    Apr 27, 2015 12:36