Updated on 2024-04-19 GMT+08:00

Notification Management

Notification Management allows users to create notification rules. Notification rules include notification scenarios and incident matching rules. When an incident ticket is generated, the notification rule first matches the incident information, then provides the O&M engineers to be notified, the notification content, and notification method, and finally sends the notification messages.

Notification templates are system built-in, including incident creation, incident rejection, incident forwarding, incident verification, incident verification failure, incident completion, and incident rejection completion templates. You can select a notification template based on your scenario.

Creating a Notification

Create a notification rule. After an incident ticket triggers the corresponding scenario, a notification is automatically sent.

  1. Log in to COC.
  2. In the navigation pane on the left, choose Basic Configurations > Notification Management. On the displayed page, click Create Notification.

    Figure 1 Clicking Create Notification

  3. Enter the parameters for creating a notification and click OK. Table 1 describes the parameters for creating a notification.

    Figure 2 Entering the notification parameters
    Table 1 Notification parameters

    Parameter

    Mandatory

    Radio/Checkbox

    Description

    Name

    Yes

    /

    Notification name of a notification instance. Fuzzy search can be performed based on the notification name.

    Type

    Yes

    Radio

    Currently, Incident Notification is the default value.

    Template

    Yes

    Checkbox

    Notification content template is system built-in. The template list varies depending on the notification type. After a template is selected, the notification template details are displayed.

    Notification Scope

    Yes

    Checkbox

    Select a service. For example, if service A is selected and service A is displayed in the incident ticket, the subscription takes effect and a notification is sent based on the subscription instance without considering other matching rules.

    Recipient

    Yes

    If Shift is selected, you can select single scenario and multiple roles. If Individual is selected, you can select multiple users.

    Objects to be notified. If Shift is selected, the notification module automatically obtains the list of personnel in the current schedule mode and sends notifications to the corresponding personnel. If Individual is selected, the notification module directly sends notifications to the corresponding users.

    Notification Rule

    /

    /

    For example, if the value of rule A is set to a, in an incident ticket, the value of rule A is a, not considering other matching rules, the subscription instance will take effect and a notification is sent based on the subscription instance. However, if the value of rule A in the incident ticket is b, the subscription instance will not take effect, and no notification is sent.

    Notification Rule - Level

    Yes

    Checkbox

    Level of an incident ticket. There are five levels: P1 to P5. For details about the incident ticket levels, see section "Creating an Incident".

    Notification Rule - Incident Category

    Yes

    Checkbox

    Category of an incident ticket. Multiple values are available.

    Notification Rule - Source

    Yes

    Checkbox

    Source of an incident ticket. Manual creation indicates that the incident ticket is created in the incident ticket center. Transfer creation indicates that the incident ticket is generated during the transfer.

    Notification Rule - Region

    No

    Checkbox

    Region of an incident ticket. Multiple regions can be selected.

    Method

    Yes

    Checkbox

    Notification channel.

    In the shift scenario, duplicated users will be removed. However, if multiple persons use the same mobile number, multiple same notifications are sent, which is the same as the notification logic in individual scenario.

    If no rule value is set in a rule, the rule will not be matched. For example, if no value is configured for rule A, the notification instance takes effect without matching rule A, not considering other matching rules. If rule A changes, the notification instance still takes effect without matching rule A.

    After a notification is created, it is enabled by default.

Editing Notifications

Modify an existing notification instance.

  1. Log in to COC.
  2. In the navigation pane on the left, choose Basic Configurations > Notification Management. On the displayed page, locate the notification to be modified and click Modify in the Operation column.

    Figure 3 Modifying notifications

  3. Modify the notification instance and save the modification. For details, see 3.

Deleting a Notification

  1. Log in to COC.
  2. In the navigation pane on the left, choose Basic Configurations > Notification Management. On the displayed page, locate the notification to be deleted and click Delete in the Operation column.

    Figure 4 Deleting a notification

  3. In the displayed confirmation dialog box, click OK to delete the notification instance. After the notification instance is deleted, it is not displayed in the list.

    Figure 5 Confirming the deletion

Searching for a Notification Instance

  1. Log in to COC.
  2. In the navigation pane on the left, choose Basic Configurations > Notification Management. On the displayed page, click the search box, enter the target notification information, and press Enter.

    Figure 6 Searching for notifications

    The search box supports search by notification type and notification name (fuzzy search). The search results can be displayed on multiple pages (10, 20, 50, or 100 records per page). Click the drop-down arrow on the left of each notification instance displays details.

Enabling and Disabling a Notification Instance

  1. Log in to COC.
  2. In the navigation pane on the left, choose Basic Configurations > Notification Management. On the displayed page, locate the notification to be enabled or disabled, click Enable or Disable in the Operation column.

    Figure 7 Enabling/Disabling Notifications

  3. The confirmation dialog box is displayed. Click OK.

    Figure 8 Confirming the enabling

    The notification instance statuses include Enabled (in green) and Disabled (in red).

Other Notification Features

The following notification features are not displayed on the page:

  1. Notification deduplication

    When an incident ticket change triggers multiple notifications, and the subscriber or other conditions of multiple notifications are the same, the notification module deduplicates the recipients, ensuring that the recipients receive only one notification when an incident ticket change occurs.

  2. Notification Template Description

    Different templates correspond to different scenarios. When an incident ticket matches a scenario, a notification can be sent. The notification templates are described as follows:

    • Incident creation: A notification needs to be sent after an incident is created.
    • Event rejection: A notification is sent after an event is rejected.
    • Incident forwarding: A notification is sent after an incident is forwarded.
    • Incident verification: A notification is sent when an incident enters the to-be-verified state after being resolved.
    • Incident completion: A notification is sent after an incident is processed and verified.
    • Incident verification failed: A notification is sent when an incident enters the to-be-verified state and fails to pass the verification.
    • Incident close after rejection: After an incident is rejected, a notification is sent after the incident is closed.