The request body of this method takes a JSON-serialized query. Some query types (e.g., task queries) allow to specify EL expressions in their parameters and may therefore be abused for remote code execution. See the section on security considerations for custom code in the user guide for details.

Method

POST

Parameters

Result

A JSON object corresponding to the corresponding entity interface in the engine. This dependson the saved query in the filter. Therefore it is not possible specify a generic result format,i.e., if the resource type of the filter is Task the result will correspond to the Taskinterface in the engine.

Response Codes

Code Media type Description
200 application/json Request successful.
200 application/hal+json Request successful. In case of an expected response.
204 Request successful, but the result was empty.
400 application/json The executed filter returned more than one single result or the extending query was invalid. See the Introduction for the error response format.
403 application/json The authenticated user is unauthorized to read this filter. See the for the error response format.
404 application/json Filter with given id does not exist. See the Introduction for the error response format.

Example

POST filter/aTaskFilterId/singleResult

Note: The examples show a task filter. So the request body corresponds to a task query. For other resource types the request body will differ.

Status 200.

  1.   "assignee": "jonny1",
  2.   "caseDefinitionId": null,
  3.   "caseExecutionId": null,
  5.   "created": "2014-09-15T15:45:48.000+0200",
  6.   "delegationState": null,
  7.   "description": null,
  8.   "due": null,
  9.   "executionId": "aExecutionId",
  10.   "formKey": null,
  11.   "id": "aTaskId",
  13.   "owner": null,
  14.   "parentTaskId": null,
  15.   "priority": 50,
  16.   "processDefinitionId": "aProcessId",
  17.   "processInstanceId": "aProcessInstanceId",
  18.   "suspended": false,
  19. }