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.

Basic concepts about users and tasks

andregs

Hi,

Could you please explain the different relationships between users and tasks?
- Owner
- Assignee
- Candidate
- Involved

I also don't understand the difference between reassign, transfer and delegate a task.

Related topics:
- http://forums.activiti.org/en/viewtopic.php?f=6&t=2043
- http://forums.activiti.org/en/viewtopic.php?f=6&t=2237

Thanks,

Find more posts tagged with

Comments

heymjo

Yes, this would be helpful.

http://forums.activiti.org/en/viewtopic.php?f=9&t=2246 is also relevant (explains Queued Tasks which is not an API semantic but appears in the Explorer)

mhw

Hi,

I am very interested, too. I do not understand why activiti:candidateUsers="accountancyUser" does not lead to

List<Task> myTasks =<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; processEngine.getTaskService().createTaskQuery().processDefinitionId(processInstance.getId())<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .taskCandidateUser("accountancyUser").list();

beeing a list with more than zero elements.

regards, Michael

trademak

Hi,

- An owner is the user that's responsible for the user task. You can have multiple sub tasks, but there's one user, the owner, who is responsible for the task.
- As assignee is a user that's allocated to that user task, and needs to complete it.
- A candidate user is a user that can claim the user task to become the assignee. Note that there's no built-in authorization that somebody who isn't a candidate user can't claim a user task and become the assignee.
- A candidate group is a group of users that can claim the user task to become the assignee.
- An involved user is somebody that's linked to the user task. You can have only 1 assignee, but you have multiple users who can be involved in the user task.

Queued tasks are user tasks that don't have an assignee, but only candidate users / groups.

The taskCandidateUser query option should return user tasks that have been configured with activiti:candidateUsers="accountancyUser".
If it's not working please post your implementation with a test case so we can reproduce it.

Best regards,

heymjo

So owner and involved user are just implicit concepts that have no runtime meaning in the process definition ? If so then it is strange to see these things being so prominent in the api and explorer. It gives impression that they are first class concepts of bpmn modelling but when you turn to the process definition they are nowhere to be seen. I think that is where much of the confusion came from.

(also what about the transfer / reassign / delegate part?)

trademak

Hi,

Yes they are implicit concepts. I don't understand your comment about them being so prominent in the API.
Of course they are available in the API, otherwise you couldn't use them. And for a process or case management solution these concepts can be very important.
But I can understand the concepts are a bit confusing. We may need to add some explanation in the user guide.

Transfer and reassign are pretty much the same thing. Setting a new owner is called a transfer, and setting a new assignee is called a reassign.
When you delegate a task as an owner, an assignee can work on the task and resolve it. When the assignee resolves it, the task is assigned back again to the owner.

Best regards,

heymjo

well with "prominent" i meant that there is an Involved tab in the explorer and there is an api method called TaskQuery.involvedUser, whereas the Involved notion until 5.7 was not really documented.

Thanks for clearing things up though, a few more lines in the doc would be helpful indeed.

mhw

Hi,

thank you for the detailed explanation. Now I have a much better understanding. Unfortunately I am not able to get my process running as expected.

<definitions id="definitions"<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; targetNamespace="<a href="http://activiti.org/bpmn20" rel="nofollow noopener noreferrer">http://activiti.org/bpmn20</a>"<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; xmlns:activiti="<a href="http://activiti.org/bpmn" rel="nofollow noopener noreferrer">http://activiti.org/bpmn</a>"<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; xmlns="<a href="http://www.omg.org/spec/BPMN/20100524/MODEL" rel="nofollow noopener noreferrer">http://www.omg.org/spec/BPMN/20100524/MODEL</a>"><br><br>&nbsp; <process id="assigningRoles"><br><br>&nbsp;&nbsp;&nbsp; <startEvent id="begin"/><br><br>&nbsp;&nbsp;&nbsp; <sequenceFlow id="flow1" sourceRef="begin" targetRef="createReport"/><br><br>&nbsp;&nbsp;&nbsp; <userTask id="createReport" name="create the report" activiti:candidateUsers="accountancyUser"/><br><br>&nbsp;&nbsp;&nbsp; <sequenceFlow id="flow2" sourceRef="createReport" targetRef="verifyReport"/><br><br>&nbsp;&nbsp;&nbsp; <userTask id="verifyReport" name="verify the report" activiti:candidateUsers="accountancyUser"/><br><br>&nbsp;&nbsp;&nbsp; <sequenceFlow id="flow3" sourceRef="verifyReport" targetRef="end"/><br><br>&nbsp;&nbsp;&nbsp; <endEvent id="end"/><br><br>&nbsp; </process><br><br></definitions>

<br>&nbsp; // create a test user in group ROLE_EDIT<br>&nbsp; User accountancyUser = identityService.newUser("accountancyUser");<br>&nbsp; Group accountancyGroup = identityService.newGroup("ROLE_EDIT");<br>&nbsp; identityService.saveGroup(accountancyGroup);<br>&nbsp; identityService.saveUser(accountancyUser);<br>&nbsp; identityService.createMembership(accountancyUser.getId(),<br>&nbsp;&nbsp;&nbsp; accountancyGroup.getId());<br><br>&nbsp; List<Group> groups = identityService.createGroupQuery()<br>&nbsp;&nbsp;&nbsp; .groupId("ROLE_EDIT").list();<br>&nbsp; assertEquals(1, groups.size());<br><br>&nbsp; List<User> users = identityService.createUserQuery()<br>&nbsp;&nbsp;&nbsp; .memberOfGroup("ROLE_EDIT").list();<br>&nbsp; assertEquals(1, users.size());<br><br>&nbsp; accountancyUser = users.get(0);<br>&nbsp; assertEquals("accountancyUser", accountancyUser.getId());<br><br>&nbsp; // start the process<br>&nbsp; ProcessInstance processInstance = runtimeService<br>&nbsp;&nbsp;&nbsp; .startProcessInstanceByKey("assigningRoles");<br><br>&nbsp; // "accountancyUser" should have one task after the process instance was<br>&nbsp; // created<br>&nbsp; List<Task> myTasks = processEngine.getTaskService().createTaskQuery()<br>&nbsp;&nbsp;&nbsp; .processDefinitionId(processInstance.getId())<br>&nbsp;&nbsp;&nbsp; .taskCandidateUser("accountancyUser").list();<br>&nbsp; Assert.assertNotNull(myTasks);<br>// here the test fails:<br>&nbsp; Assert.assertEquals(1, myTasks.size());<br><br>&nbsp; // now see if he's involved user on any task of the the process instance<br>&nbsp; Assert.assertTrue(processEngine.getTaskService().createTaskQuery()<br>&nbsp;&nbsp;&nbsp; .processDefinitionId(processInstance.getId())<br>&nbsp;&nbsp;&nbsp; .taskInvolvedUser("accountancyUser").list().size() == 0);<br><br>&nbsp; // now add myself to the task as candidate user<br>&nbsp; processEngine.getTaskService().addCandidateUser(myTasks.get(0).getId(),<br>&nbsp;&nbsp;&nbsp; "accountancyUser");<br><br>&nbsp; // and now all of a sudden i'm involved user on the task<br>&nbsp; Assert.assertTrue(processEngine.getTaskService().createTaskQuery()<br>&nbsp;&nbsp;&nbsp; .processDefinitionId(processInstance.getId())<br>&nbsp;&nbsp;&nbsp; .taskInvolvedUser("accountancyUser").list().size() == 1);<br> }<br>

What am I doing wrong?

best regards,
Michael

frederikherema1

The ID of the process-defintion is not the same as the one of the instance (line

processDefinitionId(processInstance.getId())

 // "accountancyUser" should have one task after the process instance was<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // created<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List<Task> myTasks = processEngine.getTaskService().createTaskQuery()<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .processDefinitionId(processInstance.getId())<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .taskCandidateUser("accountancyUser").list();

mhw

Wow! Thank you for the lightspeed support. Works perfectly now, just took the processInstance.getProcessDefinitionId()So I have understood the roles concept

best regards,
Michael

frederikherema1

Always glad to help

manav1

Hi,

I have created candidate group (student) and user(john). Assigned user to group.
From Java program I had created task like below.
List<Task> taskList = taskService.createTaskQuery().taskCandidateGroup("student").list();
assertEquals(1, taskList.size());
System.out.println("found task " + taskList.get(0).getName());

Tasklist size show 1, but i am not able to see the group in Queued list in acitivity explorer. It is showing only four group.
engineering, marketing,sales and management.

Why it is not showing my candidate group?

below us bpmm xml.

<process id="RequestAuthorization" name="RequestAuthorization"
isExecutable="true">
<startEvent id="startevent1" name="Start"></startEvent>
<userTask id="usertask1" name="Travel authorization request"
   activiti:candidateGroups="student"></userTask>
<sequenceFlow id="flow1" sourceRef="startevent1"
   targetRef="usertask1"></sequenceFlow>
<userTask id="usertask2" name="Authorization approval"
   activiti:candidateGroups="coordinator"></userTask>
<sequenceFlow id="flow2" sourceRef="usertask1" targetRef="usertask2"></sequenceFlow>
<endEvent id="endevent1" name="End"></endEvent>
<sequenceFlow id="flow3" sourceRef="usertask2" targetRef="endevent1"></sequenceFlow>
</process>

Thanks

jbarrez

Cause you haven't created the 'student' group in the identiy management section yet. Once you have created it there, with the exact same name, it will show up.