anchor.diff:  
   
           The Camel task allows to send messages to and receive messages from Camel and thereby enhances the integration features of Activiti.
  -        Note that the Camel task is *not* an 'official' task 
  +        Note that the Camel task is *not* an 'official' task
           of the BPMN 2.0 spec (and it does not have a dedicated icon as a consequence).
  -        Hence, in Activiti the Camel task is implemented as a dedicated service task. 
  +        Hence, in Activiti the Camel task is implemented as a dedicated service task.
           Also note to include the Activiti Camel module in your project to use the Camel task functionality.
  -      
  +
   
   [[bpmnCamelTaskUsage]]
   
  
positive.code: 				For the input variable definition a list of process variables can be defined separated by a comma.
  				The output variable definition can only contain one variable name that will be used to store the output objects of the executed business rules in a process variable.
  				Note that the result variable will contain a List of objects. If no result variable name is specified by default org.activiti.engine.rules.OUTPUT is used.
  	   	
  
  
          The following business rule task executes all business rules deployed with the process definition:
          
  ++++++++++++++++++++++++++++++++++++++
  <programlisting format="linespecific">
  &lt;process id="simpleBusinessRuleProcess"&gt;
    
    &lt;startEvent id="theStart" /&gt;
    &lt;sequenceFlow sourceRef="theStart" targetRef="businessRuleTask" /&gt;
    
    <emphasis role="bold">&lt;businessRuleTask id="businessRuleTask" activiti:ruleVariablesInput="${order}"
        activiti:resultVariable="rulesOutput" /&gt;</emphasis>
   	
    &lt;sequenceFlow sourceRef="businessRuleTask" targetRef="theEnd" /&gt;
  
    &lt;endEvent id="theEnd" /&gt;
   
  &lt;/process&gt;
  			  </programlisting>
  ++++++++++++++++++++++++++++++++++++++
  
  
  			
  
  
  				The business rule task can also be configured to execute only a defined set of rules from the deployed .drl files.
  				A list of rule names separated by a comma must be specified for this.
  				
  ----
  
  <businessRuleTask id="businessRuleTask" activiti:ruleVariablesInput="${order}"
        activiti:rules="rule1, rule2" />
  			  
  ----
  
  
  			  In this case only rule1 and rule2 are executed.
  	   	
  
  
  				You can also define a list of rules that should be excluded from execution.
  				
  ----
  
  <businessRuleTask id="businessRuleTask" activiti:ruleVariablesInput="${order}"
        activiti:rules="rule1, rule2" exclude="true" />
  			  
  ----
  
  
  			  In this case all rules deployed in the same BAR file as the process definition will be executed, except for rule1 and rule2.
  			
  
  
  				As mentioned earlier another option is to hook in the implementation of the BusinessRuleTask yourself:
  				
  ----
  
  <businessRuleTask id="businessRuleTask" activiti:class="${MyRuleServiceDelegate}" />
  			  
  ----
  
  
  			  Now the BusinessRuleTask behaves exactly like a ServiceTask, but still keeps the BusinessRuleTask icon to visualize
  			  that we do business rule processing here.
  			
  
  [[bpmnEmailTask]]
  
  
negative.code: 
  
  				A Business Rule task is visualized the with a table icon.
  
  
  
  [[bpmnBusinessRuleTaskXML]]
  
  