[APA]The user that was first assigned to a task can not be assigned anymore when having candidate groups
Deploy an app with a process that has a user task with only one candidate group.
Start a process with user1, which is part of the group.
Claim the task with user1.
With admin user assign this task to user2 that is part of the group.
With admin user try to assign the task again to user1:
Expected result: The admin user is able to assign it to user1 again.
Actual result: The admin user is not able to assign the task to user1 again, because the user1 is not displayed in the assignee list anymore.
Yep we don't have time now to have it paginated. But is an improvement that we should have in M6 and new APIs.
Perhaps you already know, but the member API was limited to 100 results.
To avoid this limit you can pass parameter max=-1, i.g.:
will returns 2107 users, while:
will returns 100 users.
Anyway, the API can be paginated using first and max parameters.
I am testing the case of task assign to a candidateUsers and I see 2 problems:
-1) we cannot search groups by name otherwise we will get groups that were not part of the list
2) the /members api returns only X users (I guess)
Because I am not able to find the hruser that is part of hr
[This comment has been reassigned to firstname.lastname@example.org as part of the Alfresco cloud migration project. The author of this comment was siva.kumar] Not able to reproduce Actual result: i moving this to test.
We can test it together if required.