topic Advanced workflow bpm:groupAssignee problem in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/advanced-workflow-bpm-groupassignee-problem/m-p/126056#M88713 <HTML><HEAD></HEAD><BODY><SPAN>Hello,</SPAN><BR /><BR /><SPAN>I'm trying to implement an extended ad-hoc workflow:</SPAN><BR /><BR /><SPAN>- user A can assign a workflow task to user B</SPAN><BR /><SPAN>- user B manages the task. He can close it or forward to user C</SPAN><BR /><SPAN>- user C manages the task. He can close it or forward it to user A, D, …</SPAN><BR /><BR /><SPAN>The number of "task forward" steps is not predefined, it simply depends on the documents being processed.</SPAN><BR /><BR /><SPAN>My process definition looks like this:</SPAN><BR /><BR /><PRE class="language-none line-numbers"><CODE><BR />&lt;?xml version="1.0" encoding="UTF-8"?&gt;<BR /><BR />&lt;process-definition<BR />&nbsp; xmlns="urn:jbpm.org:jpdl-3.1"&nbsp; name="bnotkwf:extended"&gt;<BR /><BR />&nbsp;&nbsp; &lt;swimlane name="initiator"&gt;&lt;/swimlane&gt;<BR /><BR />&nbsp;&nbsp; &lt;swimlane name="assignee"&gt;<BR />&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; &lt;assignment class="org.alfresco.repo.workflow.jbpm.AlfrescoAssignment"&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;pooledactors&gt;#{bpm_groupAssignee}&lt;/pooledactors&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/assignment&gt; <BR />&nbsp;&nbsp; &lt;/swimlane&gt;<BR /><BR />&nbsp;&nbsp; &lt;swimlane name="repeat-assignee"&gt;<BR />&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; &lt;assignment class="org.alfresco.repo.workflow.jbpm.AlfrescoAssignment"&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;pooledactors&gt;#{bpm_groupAssignee}&lt;/pooledactors&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/assignment&gt;<BR />&nbsp;&nbsp; &lt;/swimlane&gt;<BR /><BR /><BR /><BR />&nbsp;&nbsp; &lt;start-state name="start"&gt;<BR />&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; &lt;task name="bnotkwf:submitAdhocTask" swimlane="initiator" /&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;transition name="handle" to="handle-document"&gt;&lt;/transition&gt;<BR />&nbsp;&nbsp; &lt;/start-state&gt;<BR /><BR />&nbsp;&nbsp; &lt;task-node name="handle-document"&gt;<BR />&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; &lt;task name="bnotkwf:handleDocument" swimlane="assignee"&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;event type="task-create"&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;script&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if (bpm_workflowDueDate != void) taskInstance.dueDate = bpm_workflowDueDate;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if (bpm_workflowPriority != void) taskInstance.priority = bpm_workflowPriority;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/script&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/event&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp; &lt;/task&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;transition name="forward" to="repeat-handle-document"&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/transition&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;transition name="end-task" to="end"&gt;&lt;/transition&gt;<BR />&nbsp;&nbsp; &lt;/task-node&gt;<BR /><BR />&nbsp;&nbsp; &lt;task-node name="repeat-handle-document"&gt;<BR />&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; &lt;task name="bnotkwf:repeat-handleDocument" swimlane="repeat-assignee"&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;event type="task-create"&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;script&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if (bpm_workflowDueDate != void) taskInstance.dueDate = bpm_workflowDueDate;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if (bpm_workflowPriority != void) taskInstance.priority = bpm_workflowPriority;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/script&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/event&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp; &lt;/task&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;transition name="forward" to="handle-document"&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/transition&gt;<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;transition name="end-task" to="end"&gt;&lt;/transition&gt;<BR />&nbsp;&nbsp; &lt;/task-node&gt;<BR /><BR /><BR />&nbsp;&nbsp; &lt;end-state name="end"&gt;&lt;/end-state&gt;<BR />&lt;/process-definition&gt;<BR /><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN></CODE></PRE><BR /><SPAN>The problem I have now occurs in this test scenario</SPAN><BR /><BR /><SPAN>- User A assigns a Task to group B</SPAN><BR /><SPAN>- User B (member of group B) sees the task in his list, manages it and assigns the task to group C</SPAN><BR /><SPAN>- User C (member of group C) sees the task in his list, manages it and assigns the task to group D</SPAN><BR /><BR /><SPAN>Strangely enough, the task ends up in the task lists of group B again. The users in group D never see the task. </SPAN><BR /><SPAN>It seems like the workflow instance has remembered that the first bpm:groupAssignee for the "handle-document" task was group B…</SPAN><BR /><BR /><SPAN>Is this by design? Can I override that behaviour? Is there another way to implement this?</SPAN><BR /><BR /><SPAN>Cheers,</SPAN><BR /><SPAN>Roeland.</SPAN></BODY></HTML> Tue, 18 Dec 2007 21:58:04 GMT rhofkens 2007-12-18T21:58:04Z Advanced workflow bpm:groupAssignee problem https://connect.hyland.com/t5/alfresco-archive/advanced-workflow-bpm-groupassignee-problem/m-p/126056#M88713 Hello,I'm trying to implement an extended ad-hoc workflow:- user A can assign a workflow task to user B- user B manages the task. He can close it or forward to user C- user C manages the task. He can close it or forward it to user A, D, …The number of "task forward" steps is not predefined, it simpl Tue, 18 Dec 2007 21:58:04 GMT https://connect.hyland.com/t5/alfresco-archive/advanced-workflow-bpm-groupassignee-problem/m-p/126056#M88713 rhofkens 2007-12-18T21:58:04Z Re: Advanced workflow bpm:groupAssignee problem https://connect.hyland.com/t5/alfresco-archive/advanced-workflow-bpm-groupassignee-problem/m-p/126057#M88714 <HTML><HEAD></HEAD><BODY><SPAN>* bump *.&nbsp; Anyone??</SPAN></BODY></HTML> Thu, 03 Jan 2008 10:00:38 GMT https://connect.hyland.com/t5/alfresco-archive/advanced-workflow-bpm-groupassignee-problem/m-p/126057#M88714 rhofkens 2008-01-03T10:00:38Z Re: Advanced workflow bpm:groupAssignee problem https://connect.hyland.com/t5/alfresco-archive/advanced-workflow-bpm-groupassignee-problem/m-p/126058#M88715 <HTML><HEAD></HEAD><BODY><SPAN>Note that despite the name of this thread, the correct syntax for the groupAssignee variable in the code is bpm_groupAssignee, not bpm:groupAssignee.</SPAN></BODY></HTML> Tue, 08 Jul 2008 15:38:10 GMT https://connect.hyland.com/t5/alfresco-archive/advanced-workflow-bpm-groupassignee-problem/m-p/126058#M88715 ebell 2008-07-08T15:38:10Z