Derdack

Targeted Alert Notifications – Anywhere Actions

Derdack
  • Use Cases
    • Overview
    • Enterprise IT Alerting
    • IT Managed Services
    • Mobile Alerting in Manufacuring
    • Critical Operations Alerting in Banking & Financial
    • Field Service Dispatching in Energy & Utilities
    • Use Cases in other Industries
  • Products
    • Overview
    • Enterprise Alert®
      • Overview
      • Alert Notifications
      • On-call Duty Scheduling
      • Collaboration
      • Anywhere Remediation
      • Incident Mgmt. App
      • Integrations
      • Technical Support
      • Derdack FAQ
    • SIGNL4® Cloud
    • References & More
  • How to Buy
    • Overview
    • Pricing and Quotes
    • Find a local Partner
    • Azure Marketplace
  • About Derdack
    • About
    • Careers
    • Partner Program
    • Strategic Partners
    • Contact Derdack
  • News & Blog
  • Request Demo
    • de de
  • News & Blog

    • Home
    • News & Blog
    • Technical
    • Send relevant Status Updates for Alerts to Team Managers and Members

    Send relevant Status Updates for Alerts to Team Managers and Members

    • July 12, 2016
    • Technical
    Send relevant Status Updates for Alerts to Team Managers and Members

    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>
    Please note that there are different sections for different for different languages, e.g. English and German. Each section looks like the following:
    <param name=”(Name)”> <value>(Message)</value> </param>
    (Name) describes the trigger for the particular notification message and (Message) defines the content. You can change the content of (Message) to meet your specific requirements. Please, make sure you ONLY change the content between <value> and </value>. Anything else will render the overall XML file wrong-formatted and leave Enterprise Alert in a faulty state.
    Placeholders and dynamic content
    When you look at the (Message) value, you will find that placeholders are used, e.g. %TICKET. You can use these placeholders to insert dynamic content at runtime. The following placeholders are available:
    • %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>

    Be VERY careful when changes any contents of “strings.xml” and make a backup before altering this particular XML file. XML files are particularly sensitive and you might leave Enterprise Alert in a non-working state if you make an error in XML formatting and leave an inconsistent file.

    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.

    Tagged

    alertmambermanagerstatusteamupdate

    Share

    Related Posts

    Introducing a detailed History and Resend capabilities for Emergency Callouts

    August 14, 2019

    EnterpriseAlert 2019 update 8.2.0 released

    June 26, 2019

    Meaningful Parameter Names in SNMP Events

    April 29, 2019

    Import of Active Directory Distribution Lists

    April 9, 2019

    About

    DERDACK products combine automated alert notification workflows, 24/7 duty scheduling, ad-hoc collaboration and anywhere IT troubleshooting – reducing unexpected IT downtimes at large enterprises and organizations by 60%.

    Most popular

    • Take your ITIL incident management to the next level with Enterprise Alert Take your ITIL incident management to the next level with Enterprise Alert
    • Mobile alert notifications for HP Service Manager (HPSM) Mobile alert notifications for HP Service Manager (HPSM)
    • Enterprise Alert® 2015: Flood Protection is so cool! Enterprise Alert® 2015: Flood Protection is so cool!
    • Enhancing SCOM alert notifications Enhancing SCOM alert notifications
    • On-Call Schedule Management with Auto-Rotation On-Call Schedule Management with Auto-Rotation
    • Definition of Event, Alert, Incident and Notification Definition of Event, Alert, Incident and Notification
    • Announcing Enterprise Alert 2019 Announcing Enterprise Alert 2019
    • Advanced Alert Notifications for Solarwinds delivered on premise Advanced Alert Notifications for Solarwinds delivered on premise

    Categories

    • Business (30)
    • Customers (10)
    • Energy & Utilities (4)
    • Events (22)
    • Financial & Banking (3)
    • IT Ops (11)
    • Manufacturing (3)
    • News (42)
    • Technical (89)
    • Transport & Logistics (1)

    Tags

    alert alert notification alert notifications Anywhere Resolution Anywhere Response azure customer reference Database derdack enterprise alert Enterprise Alert Enterprise Alert 2016 Gartner HPE HPE ITSM incident Incident Management Incident resolution incident response Industrie 4.0 Integration IT Alerting IT Operations Maintenance microsoft Mobile App NA User Group OMS on-call on-call schedule Operational Alerting Partnership phone PowerShell rapid response SCOM scripting scsm Skype SolarWinds NPM System Center update User Group voice Windows

    Follow us

    • Twitter
    • Facebook
    • Google +
    • LinkedIn
    • XING
    • YouTube
    • Vimeo
    • Home
    • News & Blog
    • Technical
    • Send relevant Status Updates for Alerts to Team Managers and Members

    CONTACT US:
    Intl: +49 331 29878-0

    US: +1 (202) 4 700 885
    UK: +44 (20) 88167095

    CONTACT VIA EMAIL:
    info@derdack.com

    OFFICES:
    US & Europe

    NEWSLETTER:
    Sign up here

    CAREER:
    Latest job offers

    EVENTS

    • No Upcoming Events
    • Who we help
    • Products
    • How to Buy
    • About Derdack
    • News & Blog
    • Free Trial
    • Twitter
    • Facebook
    • Google +
    • LinkedIn
    • XING
    • YouTube
    • Vimeo

     © 1999-2019 Derdack – Imprint, Privacy policy

    • Use Cases
      • Overview
      • Enterprise IT Alerting
      • IT Managed Services
      • Mobile Alerting in Manufacuring
      • Critical Operations Alerting in Banking & Financial
      • Field Service Dispatching in Energy & Utilities
      • Use Cases in other Industries
    • Products
      • Overview
      • Enterprise Alert®
        • Overview
        • Alert Notifications
        • On-call Duty Scheduling
        • Collaboration
        • Anywhere Remediation
        • Incident Mgmt. App
        • Integrations
        • Technical Support
        • Derdack FAQ
      • SIGNL4® Cloud
      • References & More
    • How to Buy
      • Overview
      • Pricing and Quotes
      • Find a local Partner
      • Azure Marketplace
    • About Derdack
      • About
      • Careers
      • Partner Program
      • Strategic Partners
      • Contact Derdack
    • News & Blog
    • Request Demo
    This site uses Google Analytics. Disable. It also uses cookies: Find out more.