Enterprise Alert can send status updates for alerts to managers and team members. For example the manager can get a notification while she is in a meeting that the issue has been solved. Or, a team member that has missed an alert gets a notification that is team mate took over.
Although Enterprise Alert provides default notification texts for these purposes, you can easily adapt the format of those notifications to fit your own needs, e.g. to follow corporate policies or user requirements. The format and content of these default notifications are stored in a file called “strings.xml” which you can find in the root directory of your Enterprise Alert installation. This XML file contains the following sections that relate to default notification messages:
- <param name=”NotifyTextTicketOpened”>…</param>
- <param name=”NotifyTextTicketAccepted”>…</param>
- <param name=”NotifyTextTicketNotAccepted”>…</param>
- <param name=”NotifyTextTicketClosed”>…</param>
- <param name=”NotifyTextTicketClosedInEventSource”>…</param>
- <param name=”NotifyTextTicketUnanswered”>…</param>
- <param name=”NotifyTextTicketFailed”>…</param>
- <param name=”NotifyTextTicketCanceled”>…</param>
- <param name=”NotifyTextTicketError”>…</param>
- %TICKET = Alert Short ID
- %TYPE = User, Team or Schedule
- %DESTINATION = Destination Name (e.g. Team12)
- %RESPONSE_SENDER = The user who changed the status of the alert
- %MSG = Description provided by the user altering the alert status, e.g. via SMS reply
- %ALERT = Policy who originally started the alert notification workflow/alarm
The default notification message to a team manager looks like:
<param name=”NotifyTextTicketOpened”>
<value>An alert with ID %TICKET was opened for the alert %ALERT to %DESTINATION.
</value>
</param>
A submitted notification message will thus at runtime look like:
“An alert with ID 123 was opened for the alert MyPolicy to MyFirstTeam”.
Example
A good change would be for instance the following:
<param name=”NotifyTextTicketOpened”>
<value>A new alarm to %DESTINATION with ID %TICKET was triggered through the following policy: %ALERT
</value>
</param>
Actually, you can tweak a lot more texts, messages and contents used in Enterprise Alert through this file but more on this in later blog articles.