anchor.diff:  
             Suppose the variable +assigneeList+ contains the values +\[kermit, gonzo, fozzie\]+.
             In the snippet above, three user tasks will be created in parallel. Each of the executions
  -          will have a process variable named +assignee+ containing one value of the 
  +          will have a process variable named +assignee+ containing one value of the
             collection, which is used to assign the user task in this example.
  -        
  +
   
   
             The downside of the +loopDataInputRef+ and +inputDataItem+
             is that 1) the names are pretty hard to remember and 2) due to the BPMN 2.0 schema restrictions
  -          they can't contain expressions. Activiti solves this by offering the 
  +          they can't contain expressions. Activiti solves this by offering the
             *collection* and *elementVariable*
             attributes on the ++multiInstanceCharacteristics++:
  -          
  +
   ++++++++++++++++++++++++++++++++++++++
   <programlisting format="linespecific">
   &lt;userTask id="miTasks" name="My Task" activiti:assignee="${assignee}"&gt;
  -  &lt;multiInstanceLoopCharacteristics isSequential="true" 
  +  &lt;multiInstanceLoopCharacteristics isSequential="true"
        <emphasis role="bold">activiti:collection="${myService.resolveUsersForTask()}" activiti:elementVariable="assignee" </emphasis>&gt;
     &lt;/multiInstanceLoopCharacteristics&gt;
   &lt;/userTask&gt;</programlisting>
   ++++++++++++++++++++++++++++++++++++++
   
  - 
  -        
  +
  +
   
   
             A multi-instance activity ends when all instances are finished. However, it is possible
  
positive.code:     public static final String EXCLUDED_OWNER = "excludedOwner";
  }
  
              
  ----
  
  
            
  
  
            Here is an example db entry for a custom identity link type _administrator_ with a single
            user (__gonzo__) and group (__engineering__) values.
              
            
  
  [[bpmnUserTaskUserCustomAssignmentTaskListeners]]
  
  
negative.code:             In the following example, the assignee will be set by calling the +findManagerOfEmployee+
              on the +ldapService+ Spring bean. The _emp_ parameter
              that is passed, is a process variable&gt;.
  
  ----
  <userTask id="task" name="My Task" activiti:assignee="${ldapService.findManagerForEmployee(emp)}"/>
  ----
  
  
              This also works similar for candidate users and groups:
  
  ----
  <userTask id="task" name="My Task" activiti:candidateUsers="${ldapService.findAllSales()}"/>
  ----
  