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.

Unclaim task

marcgr

Hi guys!!
That's my first post

. I'm noob on Activiti but I really like it.

So, I'm developing my own explorer and I have a little trouble unclaiming tasks.

That is the way how I claim:

myTask.setAssignee(idUser);
ProcessEngines.getDefaultProcessEngine().getTaskService().claim(myTask.getId(), idUser);‍‍

And trying to unclaim I've found in few posts that says "you just need to do: myTask.setAssignee(null)"…
but is not enough. That don't change anything on my database… I tryed doing:

myTask.setAssignee(null);
ProcessEngines.getDefaultProcessEngine().getTaskService().addCandidateGroup(myTask.getId(), null);‍‍

but it throws an Exception:
org.activiti.engine.ActivitiException: userId and groupId cannot both be null

It seems like doesn't know where to pool it, isn't it?
What I'm doing wrong??

Find more posts tagged with

Comments

gant

Hi,

taskService.setAssignee(task.getId(), null)
works for me.

Regards

marcgr

Hi Gant,

thanks but it doesn't work… It throws the exception too.
But maybe is a version problem (I use 5.1)… Anyway next week I'm going to update to 5.6.
I'll try with next version and if it doesn't work I'll post again

ronald_van_kuij

in 5.1 this indeed would not work. Unclaiming was implemented in 5.3 iirc. As is posted in this forum and the wiki. Please use some search functionality first next time…

frankee787

I know its a bit outdated post, but is there any difference between

taskService.setAssignee(taskId, null);
and

taskService.claim(taskId, null)
Regards,
Franklin

frederikherema1

Yes, an already claimed task will throw an exception when claimed by another user, the setAsisgnee always works…`(see javadoc)

<br>/**<br>&nbsp;&nbsp; * Claim responsibility for a task: the given user is made assignee for the task.<br>&nbsp;&nbsp; * The difference with {@link #setAssignee(String, String)} is that here <br>&nbsp;&nbsp; * a check is done if the provided user is known by the identity component.<br>&nbsp;&nbsp; * @param taskId task to claim, cannot be null.<br>&nbsp;&nbsp; * @param userId user that claims the task. When userId is null the task is unclaimed,<br>&nbsp;&nbsp; * assigned to no one.<br>&nbsp;&nbsp; * @throws ActivitiException when the user or task doesn't exist or when the task<br>&nbsp;&nbsp; * is already claimed by another user.<br>&nbsp;&nbsp; */<br>&nbsp; void claim(String taskId, String userId);<br>

frankee787

The intention is to "Release" or "Unclaim" a task. Also it will be done by the same user alone. Hence what would be the ideal way to do it ?

Regards,
Franklin

frederikherema1

The javadoc states:

<br>@param userId user that claims the task. When userId is null the task is unclaimed,<br>&nbsp;&nbsp; * assigned to no one.<br>

So use the claim(null) to 'unclaim' instead of the steAsisgnee(null).

frankee787

Thanks.

Will Do.

Regards,
Franklin