i4connected Knowledgebase 5.6

Notification Profiles

Abstract

The notification profile contains the configuration settings for publishing notifications to members of a response group. Learn more from this article!

The notification profile contains the configuration settings for publishing notifications to members of a response group. A notification profile is basically a template engine, supporting configuration of notifications via:

The notification templates can be defined under the Notification Profile List panel available via the dedicated tile, for users having the Manage messenger permission enabled.

Notification_profile_list_panel_and_tile.jpg

The Notification Profile List tile and panel

Note

Users that do not have the Manage messenger permission enabled will be only allowed to view the list of Notification Profiles, but further actions are not allowed.

View_Notif_Profile.jpg

The Notification Profile List panel in view mode

The i4connected event template notification engine can use the Scriban markup syntax to create and send notifications automatically, when certain event conditions are met. Learn more about the Scriban syntax here.

The Notification Profile List panel features the following actions:

Event Notification Settings
Abstract

Check out this article to learn how to configure the Email, SMS and Server Event Notification settings for the i4messenger.

The first step in configuring the i4messenger is the definition of the Event Notification settings. The Edit event notification settings panel can be accessed by clicking the Settings toolbar button of the Notification Profiles List panel.

Settings_button.jpg

The Settings button

In this view, the i4messenger Administrator user can configure both Email settings and SMS settings, as described below.

Edit_event_notification_settings.jpg

The Edit event notification settings panel

  • Email settings

    • Email Sender Address - the address of the sender, that will be featured in the email notification as "From".

    • Provider - the user can select either the SMTP provider or the SendGrid provider.

      • SMTP - if SMTP provider is enabled, the Edit event notification settings panel is updated to display the SMTP specific settings;

        • SMTP Server - the machine responsible of the email delivery process.

        • SMTP Port - the communication endpoint of a computer connected to a network. Can be set to port 587 (unencrypted SMTP) or 465 (for SMTP with SSL enabled).

        • Enable SSL - enables the connection method SMTP over SSL, using port 465, and applies a transport security layer to the communication.

        • SMTP User Name - The SMTP username

        • SMTP Password - The SMTP password

      • Sendgrid - if SendGrid provider is enabled, the Edit event notification settings panel is updated to display the SendGrid specific settings;

        • SendGrid Api Key - The API Key used by the application to access the SendGrid services.

  • SMS settings

    • Twilio Account SID - the security identifier of the Twilio account.

    • Twilio Auth Token - the Auth Token of the Twilio account. If there are multiple tokens, the primaty token should be applied.

    • SMS Sender Phone Number - the phone number of the sender, that will be featured in the sms notification as "From".

  • Notification Server settings

    • Server Root - the URL pointing to the current i4connected Server.

Email Event notifications
Abstract

Are you about to configure the Email event notifications? Check out this article for more details about the SMTP and SendGrid providers.

As the Event templates engine provides the possibility to send notifications via Email and SMS, the scope of present article is to describe the email notification scenario.

The event occurrence emailing is based on:

  • User filters - a combination of event and object filters.

  • Templates - the template defines the format of the sent email. Templates support placeholders so that different information from the occurrence can be written in the email.

  • Provider - SMTP email and / or SendGrid email

  • Provider settings - depending on the selected provider, the user is required to add further settings.

SMTP Provider

SMTP stands for Simple Mail Transfer Protocol, which is a communication protocol for electronic mail transmission. As described under the Edit event notification settings article, by setting the SMTP Provider, the user needs to fill in the SMTP Server, Port, Username, Password and enable or disable SSL.

SMTP_settings.jpg

SMTP Provider settings

SendGrid Provider

SendGrid is a communication platform which ensures electronic mail transmission. SendGrid provides a cloud-based email delivery service that assists email delivery.

By setting the SendGrid provider, the user is requested to fill in the SendGrid Api Key, as described under the Edit event notification settings article.

Sendgrid_setings.jpg

The SendGrid Provider settings

SMS Event notifications
Abstract

Configure your SMS Event notification was never easier! Check out this article to learn how to do it by yourself!

The event notifications can be delivered via SMS, through the Twilio provider. Twilio is a cloud communications platform which allows its users to perform communication functions, such as sending and receiving text messages.

As described in the Edit event notification settings article, the SMS settings expect the Twilio Account SID, the Twilio Auth Token and the Sender Phone Number.

SMS_settings.jpg

The SMS Provider settings

Unlike the emailing workflow, the SMS event notifications are limited to a total amount of 160 alpha-numeric characters per SMS. Twilio does not support batching notifications, instead each notification is sent out as a separate message.

On the other hand, the benefit of this provider is the delivery speed which pushes the event notifications through the channel.

Viewing, filtering and refreshing Notification Profiles
Abstract

Get an insight into the Notification Profiles and learn more details about the list view, the filtering mechanism and the refresh option.

The Notification Profile List displays all the notification templates available in the i4connected portal.

Notification_profile_List.jpg

The Notification Profile List

The Notification Profiles are displayed as cards in a scrollable list providing the user with the following information:

Notif_Profile_card.jpg

The Notification Profile card

  • Notification profile name

  • Notification profile description

  • Notification profile status (Active or Inactive)

The list of Notification Profiles features a filtering mechanism, allowing the user to easily pin-point the desired event template.

filtering.jpg

Example of filter applied to the list view

Tip

For a detailed description of the simple filtering mechanism, please also visit the Simple Filter article.

By clicking the Refresh toolbar button, the list of Notification Profiles is refreshed to display the most updated version of the page.

Refresh_button.jpg

The Refresh button

Adding new Notification Profiles
Abstract

Check out a complex explanation providing you the means to create new Notification Profiles for the i4messenger application.

The Notification Profiles List panel allows the system administrator to create new event templates, by clicking the Add toolbar button.

Add_button.jpg

The Add button

The Add notification profile panel allows the user with possibility to create notification templates for either Email or SMS.

Add_notification_profile_panel_new.jpg

The Add notification profile panel

  • Name (required) - the name of the notification template.

  • Description - the description of the notification template.

  • Active toggle button - set the notification template to active or inactive. By default, the entity is set to Active.

  • Provider type (required) - the type of delivery being either Email or SMS. Based on the selected Provider type, the settings will be automatically updated.

  • Email subject (required) - the subject of the email event notification. This setting will be displayed, only if the Provider type is set to Email.

    The complete Scriban syntax is supported in this view, as well as the data model behind, consisting of a collection of occurrences {{ IEnumerable.occurrence }} and accessible using the Scriban syntax.

    Example:

    New {{ occurence.EventName }} alarms

  • Email body / SMS body - the body of the event notification.

    • Email body - when sending an Email, the user is not limited to how much text can be used. Hence, the Email body field provides the following features:

      Email_body_area.jpg
      • possibility to insert an Email Snippet. Read more details about the Email Snippets in the upcoming article.

        Email_snippet.jpg
      • various text editing features, allowing the user with possibility to input multiple fonts, font sizes, coloured highlights, coloured backgrounds, alignment options, different heading formats and bullet or numbered lists.

        Email_body.jpg
      • Source code editor

        Source_code_editor_button.jpg

        When clicking the Source code button, the Source code editor opens the Email body text is a separate window, allowing the user to edit the actual source XML.

        Source_code_window.jpg
      • Insert / Edit Link selector

        Insert_link_button.jpg

        When clicking the Insert / Edit Link button a separate window is opened allowing the user to fill in the target URL, the text of link that will be displayed by the Email notification, the Link title and the opening behavior (open in current window or open in new window).

        Insert_link_window.jpg

        Existing hyperlinks can be managed  by means of right click and selecting the desired option from the pop-up modal window. The pop-up modal dialog allows the user to edit, remove or open the link.

        Link_edit_options.jpg
      • possibility to resize the Email body field, in order to fit its contents, by pulling the lower right margin of the box.

        Resize_option.jpg
      • possibility to use the complete Scriban template syntax, as well as the data mode behind, consisting of a collection of occurrences {{ IEnumerable.occurrence }}.

        Tip

        Example with Scriban syntax:

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

        Example output:

        Output.jpg

        Further on, check out the list of available properties that can be used in the Scriban syntax.

    • SMS body - the Short Message Service (SMS) is limited to a total of 400 characters. By this, the SMS Body field provides the following features:

      SMS_body.jpg
      • possibility to insert a text snippet. More details about the Text Snippets can be found in the upcoming article.

        Text_snippet.jpg
      • possibility to resize the SMS body field, in order to fit its contents, by pulling the lower right margin of the box.

        Resize_sms_field.jpg
      • possibility to use the complete Scriban template syntax, as well as the data mode behind, consisting of a collection of occurrences {{ IEnumerable.occurrence }}, as long as the limit of 400 characters is considered.

        Tip

        Example with Scriban syntax

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

        Example output

        Ex_SMS_smaller_size.jpg

        Further on, check out the list of available properties that can be used in the Scriban syntax.

  • Subsequent message template toggle button - enables the delivery of a reminder in case the first notification did not lead to any action.

    • Subsequent email subject - allows the user with possibility to add the subject of a subsequent Email.

    • Subsequent Email / SMS body - allows the user with possibility to add the body of a subsequent Email or SMS.

  • Last message before escalation template - the toggle button that enables the delivery of one last notification, before the escalation procedure is initiated.

    • Last email subject - allows the user with possibility to add the subject of the last Email.

    • Last Email / SMS body - allows the user with possibility to add the body of a last Email or SMS.

  • Advanced settings - enables the selection of a priority filter for the notification delivery.

    Advanced_settings.jpg

    The Advanced priority settings

    Optionally, the user can select the Priority From and the Priority To to establish an advanced filtering, based on the event priorities, as follows:

    From

    To

    Filter

    Not set

    Not set

    All events will deliver notifications, regardless of their priority

    Set

    Not set

    All events having priority ranging from the value selected in the field "From" to the highest value, will deliver notifications

    Not set

    Set

    All events having priority ranging from the lowest value up to the value selected in the field "To", will deliver notifications

    Set

    Set

    All events having priority From - To, inclusively

  • Enable notification for states - the selection of a set of states for which the notification will be sent. The role of the event states is to apply additional conditions to the Notification Profiles, allowing notifications delivery to use a particular profile, when the event occurrence transitions into a certain state.

    By default, the Event starts toggle button is enabled. The below listed states are by default disabled, allowing the user to enable different behaviours, by customising the states selection, as follows:

    Enable_notification_for_states.jpg

    The notifications for states settings

    State

    Behaviour

    Event starts

    Send once when the condition matches

    Event not acknowledged

    Send on every retry when condition matches

    Event acknowledged

    Send once when the condition matches

    Event acknowledgement sla exceeded

    Send on every retry when condition matches

    Event not owned

    Send on every retry when condition matches

    Event owned

    Send once when the condition matches

    Event ownership sla exceeded

    Send on every retry when condition matches

    Event not closed

    Send on every retry when condition matches

    Event closed

    Send once when the condition matches

    Event close sla exceeded

    Send on every retry when condition matches

  • User notification throttling - the role of the notification throttling mechanism is to limit the number of notifications that are delivered. The user can choose one of the three throttle options:

    User_notification_throttling.jpg

    The User notification throttling settings

    • None - user notification throttle mechanism is turned off, hence the event occurrences are processed in real-time. All occurrences are processed as they come. Typically, this should be used only for high importance events with a low rate, otherwise it can add stress to the system and can overflow the notification mechanisms.

    • Progressive - the server will wait until a certain time elapses since the last notification processing time, then it will send the occurrences to the notification system. In case of long showers, multiple notifications can be sent at fixed intervals. The throttle interval is defined in seconds.

    • Wait All - the server will wait for occurrences to come in, until a certain time elapses since the last occurrence, then it will send them to the notification system. In case of long showers, the notifications are postponed until the shower ends and the debounce interval elapses. The throttle interval is defined in seconds.

    Note

    If enabled, the throttle mechanism buffers the occurrences and flattens them before delivery. Hence, if multiple occurrences arrive, indicating multiple transitions of the same event, only the current status will be delivered.

Notification Profile Snippets
Abstract

The Notification Profile Snippets are reusable texts supporting Scriban syntaxes, as well, that can be applied by the users as either SMS or Email bodies.

The Notification Profile Snippets are reusable texts supporting Scriban syntaxes, as well, that can be applied by the users as either SMS or Email bodies. The i4connected application provides a set of default snippets, that can be at any point reused, updated or deleted.

The Insert Snippet button is displayed when creating or updating Notification Profiles and are available in the following situations:

  • Insert Snippet for Email body

    Email_snippet.jpg
  • Insert Snippet for SMS body

    SMS_snippet.jpg
  • Insert Snippet for Subsequent Email message body

    Subsequent_email_snippet.jpg
  • Insert Snippet for Last Email message body

    Last_email_snippet.jpg
  • Insert Snippet for Subsequent SMS message body

    Subsequent_SMS_snippet.jpg
  • Insert Snippet for Last SMS message body

    Last_SMS_snippet.jpg
Email snippets

The Email Snippets can be managed in the Snippets panel by clicking the Insert snippet button, available for either Email configuration, Subsequent Email configuration or Last Email configuration sections, of the Add / Edit Notification profiles panel.

In the Email Snippets panel all the default snippets are displayed. This view features the following options:

Viewing, filtering and refreshing the Email Snippets list

The Email Snippets list displays all the snippets available for the Email Notification Profiles, regardless if they are the default ones or new snippets added by the system administrator user(s).

Email_snippets_list.jpg

The List of Email Snippets

The Email snippets are displayed as cards in a scrollable list, displaying the Snippet description.

The list of Email Snippets features a filtering mechanism, allowing the user to easily pin-point the desired snippet.

filtered_list_of_snipets.jpg

Example of filter applied to the list view

Tip

For a detailed description of the simple filtering mechanism, please also visit the Simple Filter article.

By clicking the Refresh toolbar button the list of Email snippets is reloaded to display the latest version of its contents.

Refersh_Email_snippet.jpg

The Refresh button

Adding new Email snippets

The Add toolbar button from the Email Snippets panel provides access to the Add snippet panel.

Add_snippet_panel.jpg

The Add snippet panel

To add a new Email snippet the user is required to fill in at least the mandatory fields, marked with an asterisk. By default, the user is notified about the missing mandatory information.

An Email snippet consists in:

  • Content - is the actual Email body, that will be applied in the Notification Profile and consequently delivered as email, to the Response Teams. The Snippet Content fields features the same text editing options provided by the Email body field as described in the Adding new Notification Profiles article.

  • Description - a friendly description of the Email snippet.

  • Example - an optional example of the Email output.

To preserve the changes made, the user can click the Save bottom button. To remove all the changes organised before saving the snippet, the user can click the Reset toolbar button. To leave the Add email snippet panel without saving any of the changes, the user can click the Close bottom button.

Editing Email snippets

It is possible to update an Email snippet by clicking the Edit button in the list view

edit_button.jpg

The Edit button

In the Edit snippet panel the user can change the snippet content, description and example.

Edit_snippet_panel.jpg

The Edit snippet panel

To preserve the changes made the user can click the bottom Save button. Otherwise, if the Edit snippet panel should be closed without saving, the Close bottom button can be selected.

Deleting Email snippets

The Edit snippet panel provides the user with possibility to remove a snippet, by clicking the Delete toolbar button.

Delete.jpg

The Delete button

The Delete snippet panel asks the user to manually fill in a deletion confirmation code

Delete_snippet_panel.jpg

The Delete snippet panel

To proceed with the delete operation the user can click the Delete bottom button. Deletion will be processed and the involved snippet will no longer be visible in the list view.

SMS snippets

Management of the SMS snippets can be processed in the Text Snippets panel by clicking the Insert snippet button, available in the configuration areas for SMS notification, Subsequent SMS notification and Last SMS notification, in the Add / Edit Notification profile panels.

In the SMS Snippets panel all the user added snippets are displayed. This view features the following options:

Viewing, filtering and refreshing the SMS Snippets list

By clicking the Insert Snippet button for SMS configuration, the Snippets Text panel is opened. In this view all the available snippets are displayed as scroll-able cards, providing the user with information about the Snippet description and example.

Snippets_Text_list.jpg

The SMS Snippets list

The simple filtering mechanism allows the user to easily find the desired snippets, in the list view.

filtered_sms_snippets_list.jpg

Example of SMS Snippets filtering

Tip

For a detailed description of the simple filtering mechanism, please also visit the Simple Filter article.

To update the list of SMS Snippets to its latest version the user can click the Refresh toolbar button.

Refresh_button.jpg

The Refresh button

Adding new SMS snippets

The Snippets Text panel provides the user with possibility to create new Snippets by clicking the Add toolbar button.

Add_buton.jpg

The Add toolbar button

In the Add snippet panel the user can fill in the snippet content, description and optionally an example. To keep the defined snippet, the user can click the bottom Save button. To discard the changes and close the panel, the user can click the bottom Close button.

Add_snippet_panel.jpg

The Add snippet panel

Editing SMS snippets

All the listed SMS snippets can be updated by clicking the Edit snippet button.

edit_SMS_snippets_button.jpg

The Edit SMS Snippets button

In the Edit snippet panel the user can update the snippet content, description and example. To preserve the organised changes the user can click the bottom Save button. By clicking the bottom Close button, the panel is closed and no changes are applied.

Edit_sms_snippet_panel.jpg

The Edit snippet panel

Deleting SMS snippets

To permanently remove an SMS Snippet, the user can select the Delete button, located in the toolbar of the Edit snippet panel.

Delete_button.jpg

The Delete button

The Delete snippet panel asks the user to manually type in the deletion confirmation code.

Delete_sms_snippet_panel.jpg

The Delete snippet panel

To proceed with the deletion operation, the user can click the bottom Delete button. The system confirms the deletion by displaying a toast message.

Writing the syntax for the Email / SMS body
Abstract

The scope of present article is to describe the steps for writing a Scriban syntax and use it in your Notification Profile.

The scope of present article is to describe the steps for writing a Scriban syntax. The Scriban syntax is a set of rules defining various combinations available in the i4connected server.

All the default.NET properties are available within the Scriban views (Email subject, Email body and SMS body) using the Scriban template syntax properties.

The syntax property can be accessed by setting the "IEnumerable.occurrence" between double curly braces "{{ }}". The properties between double curly braces, will be extracted from the server. The syntax sentence {{ for occurrence in occurrences }} marks the start of the database list of occurrence properties.

In below Example, the Event Name will be extracted from the data base.

{{ for occurrence in occurrences }}

{{ occurence.EventName }}

To facilitate the Event processing workflow, the SMS and Email notifications can contain Links, that open the i4connected portal, focused on the Online Alarms panel. The user can introduce Acknowledge Event links, Take Event Ownership links and Close Event links, directly in the syntax.

The bold element in the below syntax sentence writes a Link, opening the Online Alarms panel.

{{ for occurrence in occurrences }}

A new alarm has been triggered for {{ occurrence.eventName }} with priority {{occurrence.priority }}.

{{occurrence.closeLink}}

{{ end }}

To mark the end of the notification template, the element {{ end }} needs to be included in the Email subject, Email body and SMS body.

In below example, the {{ end }} element marks the end of the template.

{{ for occurrence in occurrences }}

New Alarm for {{ occurrence.EventName }}

{{ end }}

The Email notification can also contain Links positioned outside of the syntax, introduced by a different type of sentence: e.g. {{general.closeAllLink}}.

The bold element in the below syntax writes a Link, opening the Online Alarms panel.

{{ for occurrence in occurrences }}

A new alarm has been triggered for {{ occurrence.eventName }} with priority {{ occurrence.priority }}.

{{ end }}

{{general.closeAllLink}}

Tip

Check out all the Event occurrence properties and links in the syntax's collection of occurrences article.

Properties available to the Scriban syntax
Abstract

Here is the full list of the properties available to write the Scriban syntax and apply it in your Notification Profile.

Property

Type

Description

start

DateTime

The start date and time of the event occurrence.

end

DateTime

The end date and time of the event occurrence.

acknowledge

DateTime

The date and time when the event occurrence has been acknowledged.

comment

String

The comment of the event occurrence.

owner

String

The event occurrence owner.

source

String

The source of the event occurrence.

deviceAlias

String

The alias of the Event occurrence Source. As the Source can be a Device, the Device alias will be filled in this field, if the Device has an alias set.

area

String

The area name of the Event occurrence Source. As the Occurrence Source can be a Device, the Area where the Device is assigned will be displayed in this field.

site

String

The site name of the Event occurrence Source. As the Occurrence Source can be a Device, the Site where the Device is assigned will be displayed in this field.

organizationalUnit

String

The OrgUnit name of the Event occurrence Source. As the Occurrence Source can be a Device, the OrgUnit where the Device is assigned will be displayed in this field.

metadata

iDictionary

The metadata of the event occurrence. The "Metadata" property is a list of key-value pairs which are handled differently by the Scribban syntax. All the key-value pairs found in the server will be parsed in the notification as a list.

partId

String

The ID of the part for which the event occurrence was triggered.

eventName

String

The name of the event occurrence.

eventAlias

String

The alias name of the event occurrence.

eventDescription

String

The description of the event occurrence.

cause

String

The cause for the event occurrence.

effect

String

The effect of the event occurrence.

repair

String

The repair method of the event occurrence.

helpLink

String

The Help link for the event occurrence.

eventPriorityId

Int

The ID of the event priority.

eventPriority

String

The priority of the event occurrence.

eventGroup

String

The group of the event occurrence.

eventType

String

The type of the event occurrence.

takeOwnership

DateTime

The date and time when the event has been owned.

acknowlegedBy

String

The user who has acknowledged the event.

closedBy

String

The user who has closed the event.

acknowledgeLink

Link

The URL opening the i4connected portal, focused on the Online Alarms panel.

takeOwnershipLink

Link

The URL opening the i4connected portal, focused on the Online Alarms panel.

closeLink

Link

The URL opening the i4connected portal, focused on the Online Alarms panel.

acknowledgeAllFromNotificationLink

Link

The URL opening the i4connected portal, focused on the Online Alarms panel.

Note

This Property refers to the entire Events in the Email, so it can be placed outside of the "classical" template construction. Hence, it's should be formulated as follows:{{general.acknowledgeAllFromNotificationLink}}.

acknowledgeAllLink

Link

The URL opening the i4connected portal, focused on the Online Alarms panel.

Note

This Property refers to the entire Events in the Email, so it can be placed outside of the "classical" template construction. it's should be formulated as follows: {{general.acknowledgeAllLink}}.

takeOwnershipAllFromNotificationLink

Link

The URL opening the i4connected portal, focused on the Online Alarms panel.

Note

This Property refers to the entire Events in the Email, so it can be placed outside of the "classical" template construction. it's should be formulated as follows: {{general.takeOwnershipAllFromNotificationLink}}.

takeOwnershipAllLink

Link

The URL opening the i4connected portal, focused on the Online Alarms panel.

Note

This Property refers to the entire Events in the Email, so it can be placed outside of the "classical" template construction. Hence, it's should be formulated as follows: {{general.takeOwnershipAllLink}}.

closeAllFromNotificationLink

Link

The URL opening the i4connected portal, focused on the Online Alarms panel.

Note

This Property refers to the entire Events in the Email, so it can be placed outside of the "classical" template construction. Hence, it's should be formulated as follows: {{general.closeAllFromNotificationLink}}.

closeAllLink

Link

The URL opening the i4connected portal, focused on the Online Alarms panel.

Note

This Property refers to the entire Events in the Email, so it can be placed outside of the "classical" template construction. Hence, it's should be formulated as follows: {{general.closeAllLink}}.

Editing Notification Profiles
Abstract

It is possible to update the settings of your Notification Profiles at any point in time. Learn how to open them in edit mode.

All the listed Notification Profiles can be updated by the system administrator user. By clicking a Notification profile in the list view, the Edit notification profile panel is opened.

Listed_notif.jpg

Selecting Notification Profile in the list view

In this view, the user can change all the settings described in the Add Profile Notification article.

Edit_notification_prof.jpg

The Edit notification profile panel

In order to preserve the changes made, the user can select the Save button. Otherwise, clicking the Close button will close the panel without preserving any changes.

Deleting Notification Profiles
Abstract

The unnecessary Notification Profiles can be removed by the system administrator, at any point. Check out this article to learn how.

The Edit notification profile panel gives the system administrator user the possibility to permanently remove a Notification Profile, by clicking the Delete toolbar button.

Delete_button.jpg

The Delete button

The Delete Notification Profile panel provides the user with information concerning the impact of the deletion operation, if any is involved. To confirm the deletion, the user is required to manually type in the provided code and press the Delete button.

Delete_Notification_Profile.jpg

The Delete Notification Profile panel