Retrieves the details of a specified sensitive field in Data Security Guard.
Try it now
Test
RAM authorization
|
Action |
Access level |
Resource type |
Condition key |
Dependent action |
|
dataworks:QueryRecognizeRuleDetail |
get |
*All Resource
|
None | None |
Request parameters
|
Parameter |
Type |
Required |
Description |
Example |
| SensitiveName |
string |
Yes |
The name of the sensitive field. To obtain the name of the sensitive field, call the QuerySensNodeInfo operation or log on to the DataWorks console and go to the Data Category and Sensitivity Level page. |
Name |
| TenantId |
string |
Yes |
The tenant ID. To obtain the tenant ID, perform the following steps: Log on to the DataWorks console. Find your workspace and go to the DataStudio page. On the DataStudio page, click the logon username in the upper-right corner and click User Info in the Menu section. |
10241024 |
Response elements
|
Element |
Type |
Description |
Example |
|
object |
The response parameters. |
||
| Success |
boolean |
Indicates whether the request was successful.
|
true |
| ErrorCode |
string |
The error code. |
9990030003 |
| ErrorMessage |
string |
The error message. |
Missing parameter |
| HttpStatusCode |
integer |
The HTTP status code. |
200 |
| Data |
any |
The details of the sensitive field in the JSON format. |
{"nodeName":"basic unit overview","gmtModified":1709017449000,"hitThreshold":30,"sensitiveName":"mobile-yinni","templateId":"8222abeb-9784-4417-b420-0322926d5cbf","recognizeRulesType":2,"delete":false,"bydAccuracy":1,"colScan":"," defineType ":1,": ydAccuracy ":{" contentRule ":))," operationType ":0}," nodeParent ":" unit/unit basic information/unit basic overview "," level ":6," keyRuleId ":" 228248921215042mobile-yinni "," isDelete ":false," levelName ":" 6level "," sensitive ":false," operationType ":0," sourceName ": dsg-test-zuoyue","nodeId":"bea2fc81-90c9-45f3-b7a9-26d534208a0d","status":1} |
| RequestId |
string |
The request ID. You can locate logs and troubleshoot issues based on the ID. |
10000001 |
Examples
Success response
JSON format
{
"Success": true,
"ErrorCode": "9990030003",
"ErrorMessage": "Missing parameter",
"HttpStatusCode": 200,
"Data": "{\"nodeName\":\"basic unit overview\",\"gmtModified\":1709017449000,\"hitThreshold\":30,\"sensitiveName\":\"mobile-yinni\",\"templateId\":\"8222abeb-9784-4417-b420-0322926d5cbf\",\"recognizeRulesType\":2,\"delete\":false,\"bydAccuracy\":1,\"colScan\":\",\" defineType \":1,\": ydAccuracy \":{\" contentRule \":)),\" operationType \":0},\" nodeParent \":\" unit/unit basic information/unit basic overview \",\" level \":6,\" keyRuleId \":\" 228248921215042mobile-yinni \",\" isDelete \":false,\" levelName \":\" 6level \",\" sensitive \":false,\" operationType \":0,\" sourceName \": dsg-test-zuoyue\",\"nodeId\":\"bea2fc81-90c9-45f3-b7a9-26d534208a0d\",\"status\":1}",
"RequestId": "100000012"
}
Error codes
|
HTTP status code |
Error code |
Error message |
Description |
|---|---|---|---|
| 400 | BADPARAMETERS | Parameters are missing or in the wrong format. |
See Error Codes for a complete list.
Release notes
See Release Notes for a complete list.