anchor.diff:  --
   
   
  -[#custom-task-assignment-strategy]
  +[id='custom-task-assignment-strategy']
   == Custom Task Assignment Strategy
   A custom strategy for task assignment is created by extending the `AssignmentStrategy` interface. A custom strategy allows you to assign tasks in a way you want, rather than relying on one of the provided assignment strategies.
   
  
positive.code: 
  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
  
  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.
  
negative.code: 
  The `Content` table stores the actual binary content of an attachment. The content type is defined in the `Attachment` table. The maximum size of an attachment is 2 GB.
  
  [id='_delegations']
  [float]
  === Delegations
  
  Each task defines whether it can be escalated to another user or a group in the `allowedToDelegate` attribute of the `Task` table. The `Delegation_delegates` table stores the tasks that can be escalated (in the `task_id` attribute) and the users to which the tasks are escalated (`entity_id`).
  
  [id='_connecting_to_custom_directory_information_services']
  === Connecting to Custom Directory Information Services
  
  
  