Pooled groups and assignments

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.

ale_carraro

Hi, I had a problem with pooled groups, but (fortunately) I found a trick that solves. I ask what I understood badly:

if I have this definition everything works fine (note that corrector and publisher are defined intentionally the same way):

   <swimlane name="commdirection">
      <assignment actor-id="admin"/><!– To be the direction group –>
   </swimlane>

  <swimlane name="corrector">
    <assignment class="org.alfresco.repo.workflow.jbpm.AlfrescoAssignment">
      <pooledactors>GROUP_quality</pooledactors>
    </assignment>    
  </swimlane>
  
  <swimlane name="publisher">
    <assignment class="org.alfresco.repo.workflow.jbpm.AlfrescoAssignment">
      <pooledactors>GROUP_quality</pooledactors>
    </assignment>    
  </swimlane>

   <start-state name="start">
      <task name="bw:rcStartTask" swimlane="initiator" />
      <transition name="Send to corrector" to="correcting" />
   </start-state>

   <task-node name="correcting">
      <task name="bw:rcCorrectingTask" swimlane="corrector" />
      <transition name="sendToApprover" to="techapproving" />
   </task-node>

   <task-node name="techapproving">
      <task name="bw:rcApproving" swimlane="techdirection"/>
      <transition name="reject" to="correcting" />
      <transition name="approve" to="commapproving"/>
   </task-node>
   <task-node name="commapproving">
      <task name="bw:rcApproving" swimlane="techdirection"/>
      <transition name="reject" to="correcting" />
      <transition name="approve" to="publishing"/>
   </task-node>

   <task-node name="publishing">
      <task name="bw:rcPublishing" swimlane="publisher"/>
      <transition name="publish" to="startSigning" >
         <action class="org.alfresco.repo.workflow.jbpm.AlfrescoJavaScript">
            <script>
               for (var i = 0; i &lt; bpm_package.children.length; i++) {
            bpm_package.children[i].move(bw_rcDestFolder);
           } 
            </script>
         </action>
         </transition>
   </task-node>
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

If I 'merge' corrector and publisher swimlanes, however, when I go to 'publishing' task, no task is listed on the pooled group.

If I use users instead of groups, everything works.

What I miss?

Thanks Alex

ale_carraro

I also noted that if you return to a task that has a swimlane defined as a pooledactor for the second time, the 'error' applies, too.

ie.
A is a group,
1,2 are tasks
1 is a task with A as a swimlane.

if I do the following transitions: 0->1->2->1 at the end nobody in A see the task n.1

if I do the following: 0->1,take ownership->2->1 at the end the task is a personal (not pooled) and owned by the one that owned after step 1

I'm going to think it is a bug…