cancel
Showing results for 
Search instead for 
Did you mean: 

REST API Bug

jplaux
Champ in-the-making
Champ in-the-making
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
4 REPLIES 4

frederikherema1
Star Contributor
Star Contributor
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…

jplaux
Champ in-the-making
Champ in-the-making
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
Star Contributor
Star Contributor
Thanks for reporting, I'll fix this on master now so it get's in the 5.15 release…
Welcome to the new Hyland Connect. Get started or submit feedback.