Skip to main content

i4connected Knowledge Base

i4messenger Tutorials

Abstract

Are you about to get started with the i4messenger application? Check out these easy tutorials guiding you through the most common use cases.

Defining Email Notification Profiles using the Scriban syntax
Abstract

Open this article and learn how to define your Notification Profiles using the Scriban syntax in a few easy steps.

Please check the steps described below in order to define a new Email Notification Profile, using the Scriban syntax:

Note

For this tutorial, please make sure that your user has the Manage notification profiles permission enabled.

  1. Access the Notification Profile List panel by clicking the Notification Profiles tile.

  2. Click the Add toolbar button of the Notification Profile List panel.

  3. In the Add notification profile panel organize the following mandatory settings:

    Add_Notif_Profile.jpg

    1. Type in the Name of the new Notification Profile.

    2. Make sure that the Notification Profile is set to Active.

    3. Set the Provider type by choosing the Email option.

    4. Type in an Email subject.

    5. Fill in the Notification Profile body field the below syntax:

      Please note that, {{ for occurrence in occurrences }} Alarm with name "{{ occurrence.eventName }}" having "{{ occurrence.eventPriority }}" has been triggered.

      Start Date: {{ occurrence.start }}

      End Date: {{ occurrence.end }}

      Ack Date: {{ occurrence.acknowledge }}

      {{ end }}

  4. Click the bottom Save button to preserve your changes.

    Tip

    Before saving the new Email notification profile you can proceed with further optional settings, such as usage of subsequent messages, introduction of the last message before initiating the escalation procedure, priority filtering, various states notifications, and notification throttling mechanism settings. For more details, please visit the dedicated article, here.

Defining SMS Notification Profiles using the Scriban syntax
Abstract

Open this article and learn how to define your SMS Notification Profiles using the Scriban syntax in a few easy steps.

Please follow the steps listed below for more details about the usage of the Scriban syntax while creating an SMS Notification Profile:

Note

For this tutorial, please make sure that your user has the Manage notification profiles permission enabled.

  1. Open the Notification Profile List panel by clicking the Notification Profiles tile.

  2. Click the Add toolbar button of the Notification Profile List panel.

  3. In the Add notification profile panel organize the following mandatory settings:

    1. Type in the Name of the new Notification Profile.

    2. Make sure that the Notification Profile is set to Active.

    3. Set the Provider type to SMS.

    4. Fill in the SMS body field the below syntax:

       {{ for occurrence in occurrences }}
A new alarm has been triggered. 
With {{ occurrence.priority }} and {{ occurrence.eventName }} 
Start: {{ occurrence.start }} 
End: {{ occurrence.end }} 
{{general.closeAllLink}}
 {{ end }}

      Warning

      You can not have more than 400 characters in the SMS body field.

  4. Click the bottom Save button to preserver your changes.

    Tip

    Before saving the new SMS notification profile you can proceed with further optional settings, such as usage of subsequent messages, introduction of the last message before initiating the escalation procedure, priority filtering, various states notifications, and notification throttling mechanism settings. For more details, please visit the dedicated article, here.

Defining Telegram Notification Profiles using the Scriban syntax
Abstract

Check out this article and learn how to configure a new Telegram Notification Profile using the Scriban syntax to introduce various placeholder properties.

Check the below-listed steps to create a new Telegram Notification Profile using the Scriban syntax:

Note

For this tutorial, please make sure that your user has the Manage notification profiles permission enabled.

  1. Open the Notification Profile List panel by clicking the Notification Profiles tile.

  2. Click the Add toolbar button of the Notification Profile List panel.

  3. In the Add notification profile panel organize the following mandatory settings:

    Telegram_Notif.jpg

    1. Type in the Name of the new Notification Profile.

    2. Make sure that the Notification Profile is set to Active.

    3. Set the Provider type to Telegram.

    4. Fill in the Telegram body field the below syntax:

       ?
{{for occurrence in occurrences}}
Name: {{occurrence.eventName}}Alias: {{occurrence.eventAlias}}Description: {{occurrence.eventDescription}}Comment: {{occurrence.comment}}Priority: {{occurrence.eventPriority}} [{{occurrence.eventPriorityId}}]Group: {{occurrence.eventGroup}}Source: {{occurrence.source}}
Start: {{occurrence.start}}Acknowledge: {{occurrence.acknowledge}}Take Ownership: {{occurrence.takeOwnership}}End: {{occurrence.end}}
{{occurrence.acknowledgeLink}}{{occurrence.takeOwnershipLink}}{{occurrence.closeLink}}-----------------------------------------------------
{{end}}
portalLink{{ for occurrence in occurrences }}
A new alarm has been triggered. 
With {{ occurrence.priority }} and {{ occurrence.eventName }} 
Start: {{ occurrence.start }} 
End: {{ occurrence.end }} 
{{general.closeAllLink}}
 {{ end }}

      Note

      The Telegram application also allows the usage of emojis.

  4. Click the bottom Save button to preserver your changes.

    Tip

    Before saving the new Telegram notification profile you can proceed with further optional settings, such as usage of subsequent messages, introduction of the last message before initiating the escalation procedure, priority filtering, various states notifications, and notification throttling mechanism settings. For more details, please visit the dedicated article, here.

Configuring the Email notification mechanism
Abstract

Follow these steps and start configuring the Email notification mechanism. This tutorial is complimented with a bunch of screenshots and tips!

Given the multitude of options provided by the i4connected component, the system administrator user can customize the notification mechanism in various ways. The scope of this tutorial is to guide you through the steps required to configure a common scenario, involving Event Service Level Agreements, Escalation, and Email throttling.

In order to configure the i4messenger Email notification mechanism for i4connected Events the system administrator is required to perform the following steps:

  1. As a first step in the Email notification mechanism configuration guide, please open the Edit settings panel and fill in or check the current settings.

    Note

    The Edit settings panel is guarded by the Manage configurations permission.

    Edit_settings.jpg

  2. In this view, you are provided with various settings, allowing you to define the Email settings, SMS settings, Telegram settings, and the Notification Server settings.

    Tip

    For more details about the i4messenger notification settings, please visit the dedicated article, here.

  3. Next, open the Response Team panel and click on the Add toolbar button.

    Note

    Management of Response Teams can be done by all users having at least the Manage Response Teams permission.

  4. In the Add Response Team panel, we shall first add an Escalation Response Team. Proceed by filling in the following settings:

    Add_escalation_team.jpg

    1. Type in the name of the new Response team.

    2. Provide an optional description.

    3. Leave the Escalation Policy to None.

  5. Click the bottom Save button, in order to preserve your changes.

  6. In the Response Team panel, click again on the Add toolbar button, in order to create a new Response Team, as follows:

    Add_response_team_water.jpg

    1. Type in the name of the new Response Team.

      Note

      The Response Team names should be unique.

    2. Provide an optional description.

    3. Enable the Escalation Policy and select the option Retry Count.

    4. In the Escalate After (retries) field, set the amount of desired retries, before escalation occurs.

      Tip

      In this field, at least 3 retries should be defined, for the messaging system to be able to deliver the Subsequent and Last notification.

    5. Define the amount of Days / Hours and Minutes, before a retry occurs.

    6. Next, click on the Escalate to selector and choose the previously created Escalation Response Team.

  7. Click on the Notification Profile List tile.

  8. Proceed by clicking the Add toolbar button.

    Note

    Management of Notification Profiles is guarded by the Manage notification profiles permission.

  9. In the Add notification profile panel fill in in the following settings:

    1. Fill in the Notification Profile settings

      Notif_profile_settings.jpg

      1. Type in the name of the new Notification Profile.

      2. Add an optional description of the new Notification Profile.

      3. Make sure the Active toggle button is enabled.

    2. Select the Provider settings, by setting the desired Provider type. For this tutorial we shall define an Email Notification Profile, but you can choose the SMS or Telegram type, as well.

      Provider_setings.jpg

    3. Define the Email configuration settings, by filling in an email subject and body.

      Email_configuration.jpg

    4. Enable the Subsequent message template toggle button and fill in the email subject and body.

      Subsequent.jpg

      Tip

      The Subsequent message is the message delivered after the initial notification is sent if the ongoing alarm has not yet been processed.

    5. Enable the Last message before the escalation template toggle button and fill in the email subject and body.

      Last.jpg

      Tip

      The Last message before escalation is the message delivered before the escalation process starts if the ongoing alarm has not yet been processed.

    6. Configure the states in the Enable notification for states area, as follows:

      States_with_SLA_true.jpg

      1. The Start state is by default enabled. Leave the toggle button set to Yes.

      2. Enable the Acknowledgment SLA exceeded state, as well.

      Tip

      For more details concerning Notification states and their behavior, please visit the article describing them, here.

    7. Select the desired Notification throttling mode.

      Tip

      For more details concerning Notification throttling modes and their behavior, please visit the article describing them, here.

  10. Click the bottom Save button in order to preserve the changes made.

  11. Back in the Notification Profile List, click on the Add toolbar button, to add the template for notifying your Escalation Team.

  12. In the Add notification profile panel fill in in the following settings:

    1. Fill in the Notification Profile settings.

      Add_notification_profile_for_escalation_team.jpg

      1. Type in the name of the new Notification profile.

        Note

        The name of the Notification Profiles should be unique.

      2. Optionally add a description for the new Notification profile.

      3. Set the Active toggle button to value Yes.

    2. Organize the Provider settings and select the Email provider type.

      Provider_type.jpg

    3. Select the Email configuration settings and fill in the Email subject and body.

      escalation_mail.jpg

    4. Configure the states in the Enable notification for states area, as follows:

      States_with_SLA_true.jpg

      1. The Start state is by default enabled. Leave the toggle button set to Yes.

      2. Enable the Acknowledgment SLA exceeded state.

      Tip

      For more details concerning Notification states and their behavior, please visit the article describing them, here.

    5. Select the desired Notification throttling mode.

      Tip

      For more details concerning Notification throttling modes and their behavior, please visit the article describing them, here.

  13. Click the bottom Save button in order to preserve the changes made.

  14. Further on, return to the Response Teams panel. The list of all the Response Teams is displayed.

  15. Select the Escalation Response Team in detailed view mode.

    Esc_RT.jpg

  16. Click on the Users tile and assign the escalation users.

  17. Next, click on the Notification Profiles tile and assign the Escalation Notification Profile.

  18. Return to the Response Teams panel and select the Response Team in detailed view mode, as well.

    Normal_RT.jpg

  19. Click on the User tile of the Response Team and assign the response users.

  20. Click on the Notification Profiles tile and assign the Response Notification Profile.

  21. Next, go to your Site and open it in detailed view mode.

  22. Click on the Site Response Teams tile.

    Site_details.jpg

    Note

    Visibility of the Site Response Team tile is guarded by the Manage site response teams permission.

  23. In the Site Response Teams List click the Add toolbar button.

  24. In the Add Entity Response Team panel fill in the following settings:

    RTM.jpg

    1. Type in the Name of the new Site Response Team Mapping.

      Note

      The name should be unique.

    2. Optionally, add a Description of the new Site Response Team Mapping.

    3. Click on the Response Team field and select the Response Team created at step 4.

    4. In the Filters area, select the Event groups filters option and apply your Event (for this tutorial we have selected a Manual event).

      Tip

      By setting an Event group filter, ensures that the notification mechanism is only processed for the selected Events / Event types / Event groups.

    5. Go to the Priorities labels and select the desired priorities.

      Tip

      By setting a Priority filter, ensures that the notification mechanism is only processed for the selected Priorities.

  25. Click on the bottom Save button in order to preserve the changes made.

  26. Next, return to the Site detailed view mode and click on the Publish Manual Event toolbar button, to open the list of manual events.

    Publish_manual_event.jpg

    Note

    The Publish Manual Event button is guarded by the Publish manual events for sites permission.

  27. Find your event in the list and click on it.

  28. The Publish Manual Event panel is opened allowing you to trigger the alarm with a chosen comment and priority.

    Publish_Manual_Event.jpg

  29. Click the Publish button to proceed.

  30. An Event occurrence will be triggered.

    Tip

    For more details concerning Event occurrences, please also check the articles described in the Events Management section.

  31. As soon as the Event occurrence was triggered, the Active Alarms panel is updated. The new alarm is visible there.

    Consequently, the Response Team is notified via Email.

    Note

    The notifications delivery is guarded by the View events occurrences permission.

    start_email.jpg

  32. As soon as the Event Acknowledgement interval has been exceeded, based on the Event established Service Level Agreement, another email notification is delivered to the Response Team.

    Note

    The notifications delivery is guarded by the View events occurrences permission.

    first_email.jpg

  33. As the Notification profile created for the Response Team contains a "Subsequent email" and a "Last email before escalation" definition, the Response Team will receive two more emails, each one after another considering the applied time interval:

    Note

    The notifications delivery is guarded by the View events occurrences permission.

    1. the Subsequent email

      subsequent_email.jpg

    2. the Last notification before escalation

      last_warning.jpg

  34. Considering that no actions have been taken for the active Alarm, the escalation process will be started after the interval has passed.

    Consequently, the Escalation Team members will receive an email notification.

    Note

    The notifications delivery is guarded by the View events occurrences permission.

    Escalation_email.jpg
Managing Alarms in i4messenger MobileApp
Abstract

By following the below-described steps, you will be able to own, acknowledge and close Alarms, using the i4messenger MobileApp.

Accessing Alarms from an Email notification

Based on the i4messenger Notification Profile settings, occurring Alarms can trigger an Email or SMS notification. This tutorial guides you on how to access an Alarm on your portable device, from an Email notification:

  1. Open your Email application on your device and check the Inbox folder.

  2. An Email notification concerning the new i4connected Alarm should be available.

    email_notification.jpg

    Note

    The Email title and text are also configured in the context of i4connected Notification Profiles, as described in the Defining Email Notification Profiles using the Scriban syntax tutorial.

  3. Tap on one of the URLs describing an Alarm management activity. For this example, we shall open the "Take ownership of event" option.

  4. The i4messenger web application is opened, allowing you to either proceed with managing the Alarm (in our case "Own" Alarm) or to open the MobileApp.

    web_App_processing.jpg

    Important

    When opening an Alarm from an Email notification, for the first time on your device, the Web Application might ask you to introduce the i4connected Endpoint.

    It is also important to know that the i4connected environment should be publicly available over the internet or on the same network as you are. Otherwise, a firewall program should be installed on your device, in order to be able to establish the connection between your network and the i4connected environment.

Managing Alarms on a portable device

The i4messenger MobileApp lists all the Alarms available for your i4connected user, in a clean view. To manage one of the listed Alarms, please follow the steps described below:

  1. Open the i4messenger MobileApp on your device.

    Open_app_locally_on_device.jpg

  2. Fill in your credentials, in order to login, if you haven't done this step already.

    Login_page.jpg

  3. Tap on the desired Alarm in the list view.

    Main_view_MobileApp.jpg

  4. The selected Alarm is opened in detailed view mode, allowing you to either Own, Acknowledge, or Close.

  5. Tap on one of these management actions.

    Alarm_details.jpg

  6. A toast message pops up at the top of your screen, confirming the successful operation.

    Toast_message.jpg
In this section: