In Data Management (DMS), approval processes are associated with security rules. You can configure different approval processes for different types of tickets. This topic describes how to create an approval node and an approval template, and how to apply a new approval process.

Prerequisites

You are a database administrator (DBA) or a DMS administrator. For more information about how to view your system role, see View owned system roles.

Usage notes

DMS allows you to configure instance-level security rules so that you can customize different approval processes for different database instances or database operations. However, instance-level security rules may have the following restrictions in the actual business environment:
  • Each database instance has only one DBA, who is responsible for approving tickets. The entire approval process may get stuck if the DBA cannot respond as expected. To prevent this issue, you may need to allow multiple DBA roles to participate in an approval process.
  • If multiple business units share the same database in a database instance, each business unit must approve the tickets for their respective business operations in an approval process.

Procedure

  1. Log on to the DMS console V5.0.
  2. In the top navigation bar, click Security and Specifications. In the left-side navigation pane, click Approval Processes.
    Note If you are using the previous version of the DMS console, move the pointer over the More icon in the top navigation bar and choose System > Security > Approval Processes.
  3. Create an approval node.
    1. Click the Approval Node tab in the left-side pane.
    2. Click Create Approval Node.
    3. Set the parameters in the Create Approval Node dialog box. The following table describes the parameters.
      Parameter Required Description
      Node Name Yes The name of the approval node.
      Remarks Yes The description of the approval node.
      Approver Yes The one or more users that you want to specify as approvers for the approval node. If one of the approvers gives the approval, the ticket is submitted to the next approval node.
    4. Click Submit.
  4. Create an approval template.
    1. Click the Approval Template tab in the left-side pane.
    2. Click Create Approval Template.
    3. Set the parameters in the Create Approval Template dialog box. The following table describes the parameters.
      Parameter Required Description
      Template Name Yes The name of the approval template.
      Remarks Yes The description of the approval template.
      Approval Node Yes Click Add Node. In the Add Approval Node dialog box, click Select in the Actions column of the approval nodes that you want to use. In this example, the system node Owner and the approval node that is created in Step 3 are selected to allow multiple DBAs to participate in the approval process.
      Note The approval process is implemented based on the values of the Approval Order parameter in ascending order.
    4. Click Submit.
      After the approval template is created, you can view the ID of the approval template.
  5. Apply a new approval process.
    Note This example shows how to edit a security rule that is applied to medium-level risk approval processes. You can perform similar steps to apply a security rule to other scenarios.
    1. In the top navigation bar, click Security and Specifications. In the left-side navigation pane, click Security Rules.
    2. Find the rule set that you want to edit and click Edit in the Actions column.
    3. Click the SQL Correct tab.
    4. On the SQL Correct tab, select Risk Approval Rules as the checkpoint. Find the rule that is applied to medium-level risk approval processes and click Edit in the Actions column.
    5. In the Rule DSL field, change the template ID. Replace the ID of the original approval process with the ID of the new approval process.

Suggestions

  • We recommend that you bind a DingTalk account to each cloud account that uses DMS. This way, approvers can receive ticket approval notifications in real time and approve tickets.
  • Do not assign only one approver to an approval node. We recommend that you assign at least two approvers to each approval node and assign at least two data owners for a database.
  • You can assign a maximum of three data owners for a database. If multiple business units share the same database, you can specify these business units in an approval process by performing the following steps: Create an approval node and add the data owners of the business units as approvers. Then, add the new node instead of the system node Owner to an approval template.
  • If you have questions about approval processes, join the DingTalk group (ID: 21991247) to contact the DMS team.