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
      • Online Knowledge Base
      • Derdack FAQ
    • SIGNL4® Cloud
    • References & More
  • How to Buy
    • Overview
    • Pricing and Quotes
    • Azure Marketplace
  • About Derdack
    • About
    • Careers
    • Strategic Partners
    • Derdack Podcast
    • 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

    Enterprise Alert 9.4.1 comes with fixes and the revised version of the sentinel connector app

    February 1, 2023

    Critical System Alerts via SIGNL4

    December 29, 2022

    Enterprise Alert 9.4 Update introduces Remote Actions for hybrid scenarios and proxy support for MS Teams

    October 25, 2022

    Upgrade your shopfloor alerting with Derdack

    September 8, 2022

    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

    • Derdack Company Take your ITIL incident management to the next level with Enterprise Alert
    • Mobile alert notifications for HP Service Manager (HPSM)
    • How to forward alerts to Microsoft Teams
    • Oncall Scheduling On-Call Schedule Management with Auto-Rotation
    • Even, Alert, Incident, Notification Definition of Event, Alert, Incident and Notification
    • checking-mobile Enhancing SCOM alert notifications
    • Announcing Enterprise Alert 2019
    • who-is-on-call-sharepoint Add a live “Who is On-Call” Dashboard into Sharepoint and other Tools

    Categories

    • Business (37)
    • Cloud Services (5)
    • Consultancy (1)
    • Customers (18)
    • Energy & Utilities (7)
    • Events (23)
    • Financial & Banking (4)
    • IT Ops (19)
    • Manufacturing (8)
    • News (48)
    • Schools (1)
    • Software (9)
    • Staffing (1)
    • Support (4)
    • Technical (141)
    • Transport & Logistics (5)

    Tags

    alert alert notifications Anywhere Resolution Anywhere Response Azure azure BMC customer reference Database derdack enterprise alert Enterprise Alert Enterprise Alert 2016 Enterprise Alert 2019 Gartner HPE HPE ITSM incident Incident Management Incident resolution incident response Industrie 4.0 Integration IT Alerting IT Operations Maintenance microsoft mobile Mobile App monitoring OMS on-call on-call schedule Operational Alerting rapid response release Remote Action REST API SCOM security SolarWinds NPM System Center update User Group voice

    Follow us

    • Twitter
    • Facebook
    • 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 (804) 570-2005
    CH: +41 (31) 5391990

    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
    • LinkedIn
    • YouTube
    • Vimeo

     © 2025 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
        • Online Knowledge Base
        • Derdack FAQ
      • SIGNL4® Cloud
      • References & More
    • How to Buy
      • Overview
      • Pricing and Quotes
      • Azure Marketplace
    • About Derdack
      • About
      • Careers
      • Strategic Partners
      • Derdack Podcast
      • Contact Derdack
    • News & Blog
    • Request Demo
    Manage Cookie Consent
    We use cookies to optimize our website and our service.
    Functional Always active
    The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
    Preferences
    The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
    Statistics
    The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
    Marketing
    The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
    Manage options Manage services Manage vendors Read more about these purposes
    View preferences
    {title} {title} {title}