anchor.diff:  
   [NOTE]
   ====
  -All rules defined in the KIE Container specified by the `org.jbpm.task.assignment.rules.releaseId` property are used. 
  +All rules defined in the KIE Container specified by the `org.jbpm.task.assignment.rules.releaseId` property are used.
   ====
   
   [source,java]
  
positive.code: 
  * When created, a task usually has input variables, which are then set on `Task` instance. This applies to `beforeTaskAdded` and `afterTaskAdded` events handling.
  
  * When `Task` is completed, it usually has output variables, which are set on a task. 
  +
  The `loadTaskVariables` method should be used to populate task variables in all other circumstances.
  +
  [NOTE]
  ====
  Calling the `loadTaskVariables` method of the listener once (such as in `beforeTask`) makes it available to both `beforeTask` and `afterTask` methods. 
  ====
  
  . *Configuring the TaskEventListener*
  
negative.code:   "inner join ProductSale c " +
    "on (c.id = mv.map_var_id)");
  
  query.setTarget("Task");
  
  queryClient.registerQuery(query);
  
  // Maven dependency list shown above
  ----
  Note that `Target` instructs `QueryService` to apply default filters.
  Alternatively, you can set filter parameters manually. `Target` has the following values:
  
  [source,java]
  ----
  public enum Target {
      PROCESS,
      TASK,
      BA_TASK,
      PO_TASK,
      JOBS,
      CUSTOM;
  }
  ----
  
  Once registered, you can start with queries:
  