anchor.diff:  
   The Runtime Manager registers the Task Service with the Process Engine automatically. If you do not use the Runtime Manager, you have to set the `LocalHTWorkItemHandler` in the session to get the Task Service notify the Process Engine once the task completes. In Red Hat JBoss BPM Suite, the Task Service runs locally to the Process and Rule Engine. This enables you to create multiple light clients for different Process and Rule Engine's instances. All the clients can share the same database.
   
  -[#task_event_listener]
  +[#_task_event_listener]
   === Accessing Task Variables Using TaskEventListener
   
   Task variables can be accessed in the `TaskEventListener` for process instances.
  
positive.code: * Task information, such as task ID, name, and description.
  * Process information, such as process instance ID, process ID, and deployment ID.
  
  [#task_assignment_strategies]
  == Task Assignment Strategies
  
  {PRODUCT} enables you to automatically assign new tasks to a potential owner of the task, using one of the available task assignment strategies. You can enable and set this feature using system properties. For more information about system properties, see the `org.jbpm.services.task.assignment` and `org.jbpm.task.assignment` properties in the {URL_ADMIN_GUIDE}#system_properties[System Properties] section of the _{ADMIN_GUIDE}_.
  
negative.code: * `removeExcludedOwners()`: To remove existing excluded owners from given task.
  
  
  [#_sect_task_permissions1]
  == Task Service
  
  [#_task_service_and_process_engine]
  === Task Service and Process Engine
  
  Human tasks are similar to any other external service that are invoked and implemented as a domain-specific service. As a human task is an example of such a domain-specific service, the process itself only contains a high-level, abstract description of the human task to be executed and a work item handler that is responsible for binding this (abstract) task to a specific implementation.
  
  You can plug in any human task service implementation, such as the one that is provided by JBoss BPM Suite, or may register your own implementation. The Red Hat JBoss BPM Suite provides a default implementation of a human task service based on the WS-HumanTask specification. If you do not need to integrate JBoss BPM Suite with another existing implementation of a human task service, you can use this service. The Red Hat JBoss BPM Suite implementation manages the life cycle of the tasks (such as creation, claiming, completion) and stores the state of all the tasks, task lists, and other associated information. It also supports features like internationalization, calendar integration, different types of assignments, delegation, escalation and deadlines. You can find the code for the implementation in the jbpm-human-task module. The Red Hat JBoss BPM Suite task service implementation is based on the WS-HumanTask (WS-HT) specification. This specification defines (in detail) the model of the tasks, the life cycle, and many other features.
  
  [#_task_service_api]
  === Task Service API
  
  The human task service exposes a Java API for managing the life cycle of tasks. This allows clients to integrate (at a low level) with the human task service. Note that, the end users should probably not interact with this low-level API directly, but use one of the more user-friendly task clients instead. These clients offer a graphical user interface to request task lists, claim and complete tasks, and manage tasks in general. The task clients listed below use the Java API to internally interact with the human task service. Of course, the low-level API is also available so that developers can use it in their code to interact with the human task service directly.
  