Data Management (DMS) provides the notification feature that allows you to send notifications about the status updates of tickets and task flows. By default, the feature is enabled. You can specify notification recipients as needed. This way, these recipients can receive notifications at the earliest opportunity. This topic describes how to manage notification rules.

Prerequisites

Background information

You may need to notify relevant staff of data or schema changes, the approval status of tickets, or the execution status of task flows.

In this case, you can use the notification feature of DMS. DMS supports a variety of notification methods, such as DingTalk notifications, text messages, emails, and DingTalk chatbot messages.

By default, the notification feature is enabled for various status updates of tickets or task flows. The default notification recipients are the users who submit tickets or task flows. However, if the tickets are pending approval, the default notification recipients are the users who need to approve tickets. For more information, see Supported status updates of tickets or task flows.

Configure notification rules

You can configure notification rules for status updates of tickets or task flows as needed, and specify notification recipients for each rule.

  1. Log on to the DMS console.
  2. In the top navigation bar, move the pointer over the All functions icon and choose System > Notification.
  3. Perform the following operations on an existing notification rule as needed. You can view the notification rules that have been configured for status updates on the Notification tab.
    • Specify notification recipients
      1. Find the notification rule that you want to manage and click Modify in the Operation column.
        Note You can also select one or more user roles to which you want to send notifications in the Optional notification role column.
      2. In the dialog box that appears, select the notification recipients below Optional notification role or from the Additional notification User drop-down list as needed.

        You can specify the following types of recipients when you configure a notification rule:

        • Default notification role: DMS automatically selects a user role as the default notification recipient based on the status of tickets or task flows.

          For tickets that are pending approval, the default notification recipients are the users who need to approve the tickets. For tickets that are not pending approval and task flows that are created for task orchestration or data warehouse development, the default notification recipients are the users who submit the tickets or task flows.

        • Optional notification role: DMS displays different user roles that you can select as recipients. The displayed user roles may vary based on the status updates.

          Optional notification roles include Author, Approver, Data Owner, Instance DBA, DBA, Administrator, and Security Administrator.

        • Additional notification User: You can select other users under the current tenant as the notification recipients as needed.

          For example, if a developer changed a schema, big data developers must be notified of the change and perform required operations on the big data side in real time. This helps prevent report exceptions.

      3. Click Confirm.

        When the status of tickets or task flows changes, the specified recipients receive notifications about the status updates of tickets or task flows. A variety of notification methods can be configured as needed. For more information, see Configure personal information and notification methods.

    • Disable a notification rule

      If you do not want to receive the notifications about a specific type of status update, you can disable the notification rule that is configured for this type of status update. Find the notification rule that you want to disable and turn off Status in the Status column.

      After you disable the rule, you cannot receive notifications about this type of status update.

    • Enable or disable multiple notification rules at a time

      You can enable or disable multiple notification rules at a time.

      1. On the Notification tab, select the notification rules that you want to enable or disable.
      2. Click Batch enable or Batch disable in the upper part of the Notification tab. Batch enable or Batch disable

Supported status updates of tickets or task flows

The following table describes the status updates that DMS supports for tickets or task flows.

Feature Scenario Status update
Tickets Permission application
  • The ticket is pending approval.
  • The ticket is approved.
  • The ticket is rejected.
Data change
  • The precheck failed.
  • The ticket is to be submitted for approval.
  • The ticket is pending approval.
  • The ticket is approved.
  • The ticket is rejected.
  • The data change is successful.
  • The data change failed.
  • The task that is generated based on the ticket is pending scheduling.
  • The task that is generated based on the ticket timed out.
Data export
  • The precheck failed.
  • The ticket is to be submitted for approval.
  • The ticket is pending approval.
  • The ticket is approved.
  • The ticket is rejected.
  • The data export is successful.
  • The data export failed.
Data tracking
  • DMS failed to retrieve binlogs.
  • The ticket is to be submitted for approval.
  • The ticket is pending approval.
  • The ticket is approved.
  • The ticket is rejected.
  • The binlogs are parsed.
  • The binlogs failed to be parsed.
Database clone
  • The ticket is pending approval.
  • The ticket is approved.
  • The ticket is rejected.
  • The data is copied from the source database to the specified database.
  • The data failed to be copied from the source database to the specified database.
Test data generation
  • The ticket is pending approval.
  • The ticket is approved.
  • The ticket is rejected.
  • The test data is generated.
  • The test data failed to be generated.
Schema design
  • The schema of a table is changed.
  • The ticket is pending approval.
  • The ticket is approved.
  • The ticket is rejected.
  • The schema design is successful.
  • The schema design failed.
Table synchronization between databases
  • The precheck failed.
  • The ticket is to be submitted for approval.
  • The ticket is pending approval.
  • The ticket is approved.
  • The ticket is rejected.
  • The tables are synchronized from the source database to the destination database.
  • The tables failed to be synchronized from the source database to the destination database.
Task orchestration Task flow
  • The tasks in the task flow are run.
  • The tasks in the task flow failed.
Data warehouse development Task flow
  • The tasks in the task flow are run.
  • The tasks in the task flow failed.