anchor.diff:  * Data change
   * Need for node mapping
   
  -The best practice is to create backward compatible processes whenever possible, such as extending process definitions. For example, removing specific nodes from the process definition breaks compatibility. In such case, you must provide new node mapping in case an active process instance is in a node that has been removed. 
  +The best practice is to create backward compatible processes whenever possible, such as extending process definitions. For example, removing specific nodes from the process definition breaks compatibility. In such case, you must provide new node mapping in case an active process instance is in a node that has been removed.
   
   A node map contains source node IDs, from the old process definition, mapped to target node IDs in the new process definition. You can map nodes with the same type only, for example a user task to a user task.
   
  
positive.code: 
  === Exclude Potential Owner from a Human Task
  
  You can prevent a potential owner of a task from becoming the actual owner. When you exclude potential owners from a human task, they can not claim and act on it, nor can they view it in their task list. 
  To exclude users from a human task, set the task input variable with name `ExcludedOwnerId` to the name of the user you wish to exclude from the potential owner list. For this, ensure that the human task is assigned to a group. To exclude multiple owners from a human task, set the `ExcludedOwnerId` parameter to a comma separated list of values.
  
  The following BPMN process shows how to exclude a potential owner from a human task:
  
negative.code: 
  QueryServicesClient queryClient = kieServicesClient
    .getServicesClient(QueryServicesClient.class);
  
  // Maven dependency list shown above
  ----
  
  