Data Management (DMS) allows DMS administrators to manage system configurations. If you are a DMS administrator, you can modify the system configuration items to flexibly meet your business requirements. This topic describes how to modify the system configuration items.
Prerequisites
You are a DMS administrator. For more information about how to view the role of a user, see View system roles.
Procedure
- Log on to the DMS console V5.0.
In the top navigation bar, click O&M. In the left-side navigation pane, click Configuration Management.
NoteIf you use the DMS console in simple mode, move the pointer over the
icon in the upper-left corner of the DMS console and choose All functions > O&M > Configuration Management. On the Configuration Management page, find the configuration item that you want to modify and click Change in the Actions column.
NoteFor more information about configuration items, see the Configuration items section of this topic.
In the Change Parameter Configuration dialog box, change the value based on your business requirements.
Click Confirm Change.
Configuration items
Configuration item | Description |
Whether to enable access source IP control | Valid values:
|
Whether to enable automatic synchronization of instance resources on the cloud | Valid values:
|
Whether large table archive notification is enabled in SQLConsole | Valid values:
|
Data export reason classification | The reason for a data export. The possible reasons are classified into the following categories:
|
The whitelist of users who are allowed to create a task flow. | Specifies one or more users who are allowed to create task flows. |
List of disabled functional modules | Specifies one or more features that you want to disable. After a feature is disabled, the entry point of the corresponding operation is hidden. |
Access control is enabled for new users by default | Valid values:
|
Enable SQL statement field sensitive level propagation (prerequisite: Sensitive Data protection is enabled for the instance) | Valid values:
|
Whether to enable RAM permission verification | Valid values:
|
Allow sub-accounts to automatically join the tenant | Valid values:
|
Whether to force rollback SQL to be entered when submitting a data change work order, Y indicates that rollback SQL must be entered, and N indicates that rollback SQL is not to be force entered | Valid values:
|
Whether to enable the super SQL mode. | Valid values:
|
The timeout period for the number of rows affected by data change verification. | The timeout period for calculating the number of rows that may be affected. The value must be an integer. Before a data change is performed, DMS calculates the number of rows that may be affected. The calculation takes a long period of time if the data volume is large. You can specify a timeout period for the calculation in seconds to ensure that the data change can be performed as required. DMS automatically terminates the calculation after the specified timeout period. |
Data Change reason classification | The reason for a data change. The value must be a JSON string. For more information, see the Appendix: Reasons for data changes section of this topic. |
How data changes are performed | Valid values:
|
Whether the approval node of the approval flow automatically eliminates the submitter (valid when there are multiple approvers) | Valid values:
|
Unauthorized Approval Configurations for Workflow | Specifies whether to allow users who do not have the permissions to approve the specified types or all types of tickets to participate in the approval processes of tickets.
|
Minimum Word Limit for Work Order Business Background | The minimum number of characters that are entered to describe the business background of a ticket. If the value is less than or equal to 0, no limits are imposed on the number of characters. |
Allow OWNER to authorize users | Valid values:
|
Maximum number of queries for the day | The maximum number of queries that each user is allowed to perform per day. The value must be an integer. After the number of queries that a user performs in a day reaches the specified upper limit, the user cannot perform more queries for the rest of the day. This configuration item applies to all the users within the current tenant account. |
Day query rows upper limit | The maximum number of data rows that can be returned to each user per day. The value must be an integer. After the number of data rows that are returned to a user in a day reaches the specified upper limit, the user cannot perform more queries for the rest of the day. This configuration item applies to all the users within the current tenant account. |
Redis gets the maximum number of polls for the key list. | The maximum number of polls for the key list that Redis gets. The value must be an integer. If the value is less than or equal to 0, no limits are imposed on the number of polls. |
Maximum number of returned rows for cross-database queries | The maximum number of rows returned for cross-database queries. The value must be an integer. Default value: 100. Maximum value: 3000. |
DMS locale: ZH/EN/JA/ZT | The language of the operation logs that are returned by DMS. Valid values:
|
[Data Security] Anti-leakage Digital Watermarking Function | Specifies whether to enable anti-leakage digital watermarking. Valid values:
|
Watermark for Exported SQL Result Sets | Valid values:
|
Appendix: Reasons for data changes
DMS provides the following default reasons for data changes, in the format of JSON strings:
[{"key":"config_correct","value":"Modify Config"},
{"key":"project_init_data","value":"Init Project Data"},
{"key":"program_bug","value":"Program Bug"},
{"key":"require_deal_without_backend_function","value":"Requirements Without Backend Function"},
{"key":"history_data_clear","value":"History Data Clean"},
{"key":"test","value":"Test"},
{"key":"mis_operation","value":"Mis Operation"},
{"key":"others","value":"Others"}]The following table describes the default reasons for data changes.
key | value | Description |
config_correct | Modify Config | Modify configuration items |
project_init_data | Init Project Data | Initialize the data for a project |
program_bug | Program Bug | Fix a bug |
require_deal_without_backend_function | Requirements Without Backend Function | Manage the data of an application that does not support backend management |
history_data_clear | History Data Clean | Clear historical data |
test | Test | Perform a test |
mis_operation | Mis Operation | Restore data after an accidental operation |
others | Others | Change data for other reasons |