anchor.diff:  ++++++++++++++++++++++++++++++++++++++
   
   
  -  
  +
   
   
     The example class below uses the injected expressions and resolves them using the current +DelegateExecution+.
  
positive.code: 
  The shell task is implemented as a dedicated <<bpmnJavaServiceTask,Service Task>>
  		      and is defined by setting _'shell'_ for the _type_ of the service task.
  		      
  ++++++++++++++++++++++++++++++++++++++
  <programlisting format="linespecific">
  &lt;serviceTask id="shellEcho" <emphasis role="bold">activiti:type="shell"</emphasis>&gt;		      
  		      </programlisting>
  ++++++++++++++++++++++++++++++++++++++
  
  
  		    
  
  
  		      The Shell task is configured by <<serviceTaskFieldInjection,field injection>>.
  
negative.code: ++++++++++++++++++++++++++++++++++++++
  
  
  
  
  
            Tasks defines with the _potential owner_ construct, can be retrieved as follows
            (or a similar _TaskQuery_ usage as for the tasks with an assignee):
  
  ----
  
   List<Task> tasks = taskService.createTaskQuery().taskCandidateUser("kermit");
  ----
  
  
  
            This will retrieve all tasks where kermit is a *candidate user*,
            i.e. the formal expression contains _user(kermit)_. This will also
            retrieve all tasks that are *assigned to a group where kermit is a member of* (e.g. _group(management)_, if kermit is a member of that group
            and the Activiti identity component is used).
            The groups of a user are resolved at runtime and these can be
            managed through the <<apiEngine,IdentityService>>.
  
  
  
            If no specifics are given whether the given text string is a user or group,
            the engine defaults to group. So the following would be the same as when
            _group(accountancy) was declared_.
  
  ----
  
  <formalExpression>accountancy</formalExpression>
  ----
  
  
  
  
  [[bpmnUserTaskUserAssignmentExtension]]
  
  