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_escalation]
  == Task Escalation
  
  It is possible to implement Task Escalation for your Human Tasks to set up a timer within which certain task must be finished. To learn more about Task Escalation, see {URL_USER_GUIDE}#escalation[A.3.2. Escalation] from {USER_GUIDE}. Red Hat JBoss BPM Suite also supports custom implementation of the Email Notification Events in the Task Escalation service, which requires you to do the following:
  
negative.code: 
  The `Reassignment` table refers to the `Escalation` table: the `Escalation_Reassignments_Id` attribute in `Reassignments` is equivalent to the `id` attribute in `Escalation`.
  
  [#_notifications]
  [float]
  === Notifications
  
  