topic Re: Restrictions on candidate users in Alfresco Archive

Restrictions on candidate users

shr — Thu, 13 Mar 2014 09:59:50 GMT

Hello,for a "Review document" workflow I have the requirement that a task shall not be claimed by the author of the document even if he/she is in candidateGroups. Assume the author's name is stored in a process variable. I guess it is possible to do so programmatically (Script task, or service call

Re: Restrictions on candidate users

jbarrez — Mon, 17 Mar 2014 08:42:33 GMT

That's a tricky requirement … even with scripts/expression it would be hard to do since the candidate group is in there.
The way I see it, it must be done in a layer above Activiti, and it needs to be filtered out there.

Re: Restrictions on candidate users

shr — Mon, 17 Mar 2014 09:07:50 GMT

Thanks for your assessment. So you are suggesting to feed a list of the eligible users to Activiti's candidateUsers? candidateUsers seems to accept JUEL expressions, so I'll have a look into these.

Re: Restrictions on candidate users

jbarrez — Mon, 17 Mar 2014 10:34:45 GMT

No, the problem is that the query will always use the candidategroups.

I think you need to write custom logic around this query that filters out the response when the owner fetches the task list

Re: Restrictions on candidate users

shr — Mon, 17 Mar 2014 11:04:43 GMT

I think we have a misunderstanding here. Let me elaborate: Instead of [php]candidateGroup="reviewers"[/php] I was going to try something along the lines of [php]candidateUsers="${util.allExcept(reviewers, author)}"[/php]. The method would then query for tasks like [php]taskService.createTaskQuery().active().taskCandidateGroup(reviewers).list()[/php] and additionally filter the author from the list. Maybe that is also what you are suggesting. There are probably more ways how and where to apply the filtering, but this is the one solution I can think of at the moment.

Re: Restrictions on candidate users

jbarrez — Wed, 19 Mar 2014 14:25:13 GMT

Yes, we're talking about the same thing, but you're solution is probably better. You can indeed use a custom bean in those expressions to do what you need.

Re: Restrictions on candidate users

shr — Wed, 19 Mar 2014 14:31:37 GMT

Cool. Thanks for sharing your perspective.