Notification Management
Notification Management creates notification rules for users. Notification rules include incident notifications, change notifications, and issue notifications.
When an incident ticket, issue ticket, or change ticket is generated, the notification rule and the information about the incident, issue, or change are matched, then the recipients, the notification content, and notification method are obtained through parsing, and finally the notification messages are sent.
The incident and change notification templates are preset in the system. You can select a notification template as needed.
Creating a Notification Rule
Create a notification rule. After an incident, issue, or change ticket matches the corresponding rule, a notification is automatically sent.
- Log in to COC.
- In the navigation pane on the left, choose Basic Configurations > Notification Management. On the displayed page, click Create Notification.
Figure 1 Clicking Create Notification
- In the displayed dialog box, enter the notification configuration information and click OK. Table 1 described the required parameters.
Figure 2 Setting 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
Including incident notifications, change notifications, and issue notifications.
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
No
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
No
Checkbox
Category of an incident ticket. Multiple values are available.
Notification Rule - Source
No
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.
- Log in to COC.
- In the navigation pane on the left, choose Basic Configurations > Notification Management. Locate the notification to be modified and click Modify in the Operation column. Modify and save the notification by referring to the 3.
Figure 3 Modifying notifications
Deleting a Notification
- Log in to COC.
- In the navigation pane on the left, choose Basic Configurations > Notification Management. Locate the notification to be deleted and click Delete in the Operation column.
Figure 4 Deleting a notification
- In the displayed confirmation dialog box, click OK to delete the notification. After the notification is deleted, it is not displayed in the list.
Figure 5 Confirming the deletion
Searching for a Notification Instance
- Log in to COC.
- In the navigation pane on the left, choose Basic Configurations > Notification Management. Enter the search criteria in the search box 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
- Log in to COC.
- In the navigation pane on the left, choose Basic Configurations > Notification Management. Locate the notification to be enabled or disabled and click Enable or Disable in the Operation column.
Figure 7 Enabling/Disabling a Notification
- 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:
- Notification deduplication
When an incident ticket or a change ticket triggers multiple notifications, and the recipients or other factors of these notifications are the same, the notification module deduplicates the recipients, ensuring that a recipient receive only one notification when an incident or change ticket is generated.
- Notification Template Description
Incident notification template: 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.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot