added a comment - - edited
Oops, wrong key pressed, now can't finish my entry. So here is the missing description of this issue.
When obtaining task details via the REST API using the request:
GET /tasks?[assignee={userId}|candidate={userId}|candidate-group={groupId}][&start=0][&size=10]
the JSON response contains unescaped control characters. The easiest way to reproduce this is to use the process "financialReport" from the demo setup.
This is where the problem becomes clear (see the [description] field, after the first sentence there is a new line character, you can't see it here):
"data": [
{
"id": 292,
"name": "Verify monthly financial report",
"description": "Verify monthly financial report composed by the accountancy departement.
This financial report is going to be sent to all the company shareholders.",
"priority": 2,
"assignee": null,
"executionId": 285
}
]
,
"total": 1,
"start": 0,
"size": 10,
"sort": "id",
"order": "asc"
}
There is a "new line" character in the description of the above task, which causes an error when decoding such malformed JSON data.
Bug
Resolved
Major
Oops, wrong key pressed, now can't finish my entry. So here is the missing description of this issue.
When obtaining task details via the REST API using the request:
GET /tasks?[assignee={userId}|candidate={userId}|candidate-group={groupId}][&start=0][&size=10]
the JSON response contains unescaped control characters. The easiest way to reproduce this is to use the process "financialReport" from the demo setup.
This is where the problem becomes clear (see the [description] field, after the first sentence there is a new line character, you can't see it here):
"data": [
{ "id": 292, "name": "Verify monthly financial report", "description": "Verify monthly financial report composed by the accountancy departement. This financial report is going to be sent to all the company shareholders.", "priority": 2, "assignee": null, "executionId": 285 }]
,
"total": 1,
"start": 0,
"size": 10,
"sort": "id",
"order": "asc"
}
There is a "new line" character in the description of the above task, which causes an error when decoding such malformed JSON data.