Retrieve diagnostic tree node data by keyword search
post
/custom-actions/diagnosticTreeNodeByKeyword
Returns the diagnostic tree node details for given matching search keyword. A search is conducted on entire node data, like status, remarks, process name, and entities.
Request
There are no request parameters for this operation.
Supported Media Types
- application/json
Root Schema : schema
Type:
Show Source
object-
diagnosticLogFileId(required): string
The diagnostic log file identifier.
-
filterMap: object
filterMap
Nested Schema : filterMap
Type:
Show Source
object-
searchKeyword(required): string
The search keyword in diagnostic tree nodes. The search is conducted on the entire node data like status, remarks, process name, and so on.Example:
multistop
Response
Supported Media Types
- application/json
200 Response
The successful response.
Root Schema : DiagnosticTreeNodeByKeywordResponse
Type:
Show Source
object-
actualDepth(required): integer
The total depth of the given diagnostic tree data.
-
completeTree(required): boolean
-
reason: string
Shows the error reason in the case where the matched tree node is larger in size.
-
requestedDepth(required): integer
The requested depth of the tree. This represents the depth parameter in the rest request.
-
returnedDepth(required): integer
The eturned depth of the tree.
-
status(required): string
The status of the process: SUCCESS or FAILURE.
-
tree(required):
TreeNode
Nested Schema : TreeNode
Type:
Show Source
object-
childIds: array
childIds
The list of child node IDs.
-
children: array
children
The recursive child nodes.
-
duration: string
The execution duration, e.g., '35.35S'
-
entities: object
entities
Additional Properties Allowed: additionalPropertiesThe dynamic entity map keys, like ORDER_RELEASE, BULK_PLAN, etc.
-
exportFiles: array
exportFiles
The list of file names like conoptData1.xml, conoptData2.xml, etc.
-
id: string
The ID of the diagnostic tree node.
-
isList: boolean
-
nonDBEntities: array
nonDBEntities
-
processType: string
The name of the current process that the node represents.
-
reasonCodeList: array
reasonCodeList
-
remarks: array
remarks
-
status: string
The status of the process. It could be SUCCESS, FAILURE, ERROR, and so on.
Nested Schema : entities
Type:
objectAdditional Properties Allowed
Show Source
The dynamic entity map keys, like ORDER_RELEASE, BULK_PLAN, etc.
Nested Schema : exportFiles
Type:
arrayThe list of file names like conoptData1.xml, conoptData2.xml, etc.
Show Source