REST API Bug

[jplaux]

Hi,

I have noticed a very little bug in rest api.
With the current api, if you want to unclaim a task, you have to claim a task with assignee = null but Rest-api throws an exception when assignee is null.
Just remove the throwing in TaskResource to solve the problem.

Jean-Pascal

[frederikherema1]

Jean-Pascal,

Thanks for reporting this. Seems like a valid fix for the problem, allowing the assignee in the payload to be null, when claiming. Will fix this in 5.15…

[frederikherema1]

See https://github.com/Activiti/Activiti/commit/57034fa44bfbaefdd2449d70cbe4da668659e687

[jplaux]

I have created code for process attachment and I have found a little bug in RestResponseFactory in createAttachementResponse.
In your code :
    if(attachment.getProcessInstanceId() != null) {
      result.setTaskUrlsecuredResource.createFullResourceUrl(RestUrls.URL_PROCESS_INSTANCE, attachment.getProcessInstanceId()));
    }

This should be :
    if(attachment.getProcessInstanceId() != null) {
      result.setProcessInstanceUrl(securedResource.createFullResourceUrl(RestUrls.URL_PROCESS_INSTANCE, attachment.getProcessInstanceId()));
    }

[frederikherema1]

Thanks for reporting, I'll fix this on master now so it get's in the 5.15 release…