I would appreciate the extension of the task endpoint in the CAMUNDA Rest API.
Any user task can hold information like candidate groups, candidate users and so on. These model emphasized textextension fields are not being provided when querying the referenced endpoint.
My recommendation is to add another query param wich contains a list of expected extension fields to be present in the endpoint’s response.
Our use case is simple: Together with our customer’s Process Manager we define (abstract) user assignments to certain tasks (by using “candidate groups”) in the CAMUNDA modeler. Now we need to provide the user with a task list he/she is assigned to, or is part of at least member one of the candidate groups assigned to a given user task.
Since the task attributes “candidate users”, “candidate user groups” seem to my extensions to the BPMN default made by CAMUNDA it might be useful to be able to include these fields into the task endpoint’s response. By naming the desired extensions fields the API could be more dynamic and therefore more future-proof (from my personal point of view).