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.

claim, setAssignee and taskAssignee

chantme

Hello

I try to make my own experience with the APIs

If I do

// case 1
Task myTask = lstCandidateTask.get(0);
myTask.setAssignee(myUser);
List<Task> lstTask = taskServ.createTaskQuery().taskAssignee(myUser).list();
‍‍‍‍‍‍

lstTask is empty

But if I do

// case 2
Task myTask = lstCandidateTask.get(0);
taskServ.claim(myTask.getId(), myUser);
List<Task> lstTask = taskServ.createTaskQuery().taskAssignee(myUser).list();
‍‍‍‍‍‍

lstTask contains the assigned task to myUser.

I know that claim checks if the task is not already assigned.

But why in the first case the task does not appear assigned to myUser ?

(I use Activiti 5.10)

Thank you

Find more posts tagged with

Comments

heymjo

<br>Task myTask = lstCandidateTask.get(0);<br>myTask.setAssignee(myUser);<br>taskServ.saveTask(myTask);<br>List<Task> lstTask = taskServ.createTaskQuery().taskAssignee(myUser).list();<br>

i agree it is not very intuitive.

chantme

Yes indeed !!

Thank you Jorg !

frederikherema1

It's a simple principle IMHO. All operations you perform on the task-service (e.g.. setAssignee and claim) are persisted immediately.

Everything you do on the Task object, should be applied by saving that object, using saveTask().

heymjo

<br>It's a simple principle IMHO. All operations you perform on the task-service (e.g.. setAssignee and claim) are persisted immediately. <br><br>Everything you do on the Task object, should be applied by saving that object, using saveTask().<br>

Sure, but logically why is there no claim|complete etc on task then ? This is the confusing bit, the fact that some operations are present on both sides but they work differently and some operations are only available on the task service.

From a technical point of view i know of course why they are this way, but it's just slightly confusing as this post demonstrates.

frederikherema1

Setting the assignee is the claim… However, this does not alter the state of a task, nor a process. Completing does, so it won't make sense to make this available in the POJO, since it impacts more than meets the eye.