anchor.diff:  
   Most of the times forms are used to display data to the end user. This allows them to generate or create new data to propagate to the process context to be used by future activities. In order to decide how the information flow from the process to a particular task and from the task to the process, you need to define which pieces of information must be automatically copied by the process engine.
   
  -[[_task_lifecycle]]
  +[#task_lifecycle]
   == Task Lifecycle
   
   A human task is created when a user task node is encountered during the execution. The process leaves the user task node only when the associated human task is completed or aborted. The human task itself has a complete life cycle as well. The following diagram describes the human task life cycle.
  
positive.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
  
  
negative.code: Not fully supported.
  
  
  [#reassignments]
  [float]
  === Reassignments
  
  