nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Rest: how to reassign a task to a different user?

f_lombardo

How could I reassign a task to a different user using REST API?

Thanks in advance.

Bye

Franco

Find more posts tagged with

Comments

jbarrez

http://activiti.org/userguide/index.html#N12B83

yes, this is a RTFM.
But at least I was friendly enough to already provide a link 😉

f_lombardo

First of all, thank you for your answer.

Then I'll try to explain my problem better.

Suppose I assigned a task to a user (e.g. kermit) with the API call you mentioned. Then I want to revert this assignment, giving this same task to a different user (e.g. gonzo). When I call that API the second time, I get an error at line 64 of the TaskOperationResource class.
This is because in class ClaimTaskCmd we can see:

<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if(!task.getAssignee().equals(userId)) {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // When the task is already claimed by another user, throw exception. Otherwise, ignore<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // this, post-conditions of method already met.<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; throw new ActivitiTaskAlreadyClaimedException(task.getId(), task.getAssignee())<br>

So how can I override this behavior?

Thank you.

Bye

Franco

f_lombardo

By the way, I'guessing if it would be better to change line 41 of class TaskOperationResource, checking for null values of the entity parameter.

Thanks.

Bye

Franco

trademak

Hi Franco,

Did you look at the latest version of TaskOperationResource? Because line 41 is an empty line.
In your use case you first have to invoke the unclaim operation on the TaskOperationResource.
Then the task can be assigned to another user.

Best regards,

f_lombardo

Sorry, I'm looking at ver 5.10 of TaskOperationResource.

I see that in the newest version of this class you introduced both the null pointer check and the unclaim operation.

Thanks a lot.

Bye

Franco