Applications detection rules API - Reorder rules
Application detection rules are evaluated from top to bottom, the first matching rule applies.
This request reorders the application detection rules according to the order of the IDs in the body of the request. Rules that are omitted in the body of the request will retain their relative order but will be placed after all those present in the request.
The request consumes an application/json payload.
| PUT |
|
Parameters
| Parameter | Type | Description | In | Required |
|---|---|---|---|---|
| body | StubList |
JSON body of the request containing the IDs of the custom services in the desired order. Any further properties (name, description) will be ignored. |
body | optional |
The StubList object
An ordered list of short representations of DESK entities.
| Element | Type | Description | Required |
|---|---|---|---|
| values | EntityShortRepresentation[] |
An ordered list of short representations of DESK entities. |
required |
The EntityShortRepresentation object
The short representation of a DESK entity.
| Element | Type | Description | Required |
|---|---|---|---|
| id | string |
The ID of the DESK entity. |
required |
| name | string |
The name of the DESK entity. |
optional |
| description | string |
A short description of the DESK entity. |
optional |
This is a model of the request body, showing the possible elements. It has to be adjusted for usage in an actual request. See the Example expandable section for working sample request.
{
"values": [
{
"id": "6a98d7bc-abb9-44f8-ae6a-73e68e71812a",
"name": "DESK entity 1",
"description": "DESK entity 1 for the REST API example\n"
},
{
"id": "ee70f7d3-9a4e-4f5f-94d2-c9d6156f1618",
"name": "DESK entity 2"
},
{
"id": "8cdabe77-9e1a-4be8-b3df-269dd6fa9d7f"
}
]
}
Response format
A successful request doesn't return any content.
Response codes
| Code | Description |
|---|---|
| 204 | Success. Application detection rules have been updated. Response doesn't have a body. |
| 400 | Failed. The input is invalid. |