All supported JSON paremeter fields allowed are exactly the same as the parameters found for <linklinkend="restTasksGet">getting a collection of tasks</link>, but passed in as JSON-body arguments rather than URL-parameters to allow for more advanced querying and preventing errors with request-uri's that are too long. On top of that, the query allows
All supported JSON parameter fields allowed are exactly the same as the parameters found for <linklinkend="restTasksGet">getting a collection of tasks</link>, but passed in as JSON-body arguments rather than URL-parameters to allow for more advanced querying and preventing errors with request-uri's that are too long. On top of that, the query allows
for filtering based on task and process variables. The <literal>taskVariables</literal> and <literal>processInstanceVariables</literal> are both json-arrays containing objects with the format <linklinkend="restQueryVariable"> as described here.</link>
</para>
<para>
...
...
@@ -4239,6 +4239,146 @@ Only the attachment name is required to create a new attachment.
<entry>Only return jobs part of a process with the given id</entry>
<entry>String</entry>
</row>
<row>
<entry>executionId</entry>
<entry>Only return jobs part of an execution with the given id</entry>
<entry>String</entry>
</row>
<row>
<entry>processDefinitionId</entry>
<entry>Only return jobs with the given process definition id</entry>
<entry>String</entry>
</row>
<row>
<entry>withRetriesLeft</entry>
<entry>If <literal>true</literal>, only return jobs with retries left. If false, this parameter is ignored.</entry>
<entry>Boolean</entry>
</row>
<row>
<entry>executable</entry>
<entry>If <literal>true</literal>, only return jobs which are executable. If false, this parameter is ignored.</entry>
<entry>Boolean</entry>
</row>
<row>
<entry>timersOnly</entry>
<entry>If <literal>true</literal>, only return jobs which are timers. If false, this parameter is ignored. Cannot be used toghether with <literal>'messagesOnly'</literal>.</entry>
<entry>Boolean</entry>
</row>
<row>
<entry>messagesOnly</entry>
<entry>If <literal>true</literal>, only return jobs which are messages. If false, this parameter is ignored. Cannot be used toghether with <literal>'timersOnly'</literal></entry>
<entry>Boolean</entry>
</row>
<row>
<entry>withException</entry>
<entry>If <literal>true</literal>, only return jobs for which an exception occured while executing it. If false, this parameter is ignored.</entry>
<entry>Boolean</entry>
</row>
<row>
<entry>dueBefore</entry>
<entry>Only return jobs which are due to be executed before the given date. Jobs without duedate are never returned using this parameter.</entry>
<entry>Date</entry>
</row>
<row>
<entry>dueAfter</entry>
<entry>Only return jobs which are due to be executed after the given date. Jobs without duedate are never returned using this parameter.</entry>
<entry>Date</entry>
</row>
<row>
<entry>exceptionMessage</entry>
<entry>Only return jobs with the given exception message</entry>
<entry>String</entry>
</row>
<row>
<entry>sort</entry>
<entry>Field to sort results on, should be one of <literal>id</literal>, <literal>dueDate</literal>, <literal>executionId</literal>, <literal>processInstanceId</literal> or <literal>retries</literal>.</entry>
<entry>String</entry>
</row>
<row>
<entrynamest="c1"nameend="c3"><para>The general <linklinkend="restPagingAndSort">paging and sorting query-parameters</link> can be used for this URL.</para></entry>
"exceptionMessage":"Can't find scripting engine for 'unexistinglanguage'",
"dueDate":"2013-06-07T10:00:24.653+0000"
},
...
],
"total":2,
"start":0,
"sort":"id",
"order":"asc",
"size":2
}</programlisting>
<table>
<title>Response codes</title>
<tgroupcols='2'>
<thead>
<row>
<entry>Response code</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry>200</entry>
<entry>Indicates the requested jobs were returned.</entry>
</row>
<row>
<entry>400</entry>
<entry>Indicates an illegal value has been used in a url query parameter or the both <literal>'messagesOnly'</literal> and <literal>'timersOnly'</literal> are used as parameters. Status description contains additional details about the error.</entry>