anchor.diff:  |NOT NULL
   
   |``createdDate``
  -|Date whentask was created
  +|Date when task was created
   |
   
   |``duration``
  
positive.code: == Variables auditing
  
  
  Process and task variables are stored in autdit tables by default although there are stored in simplest possible way - by creating string representation of the variable - variable.toString(). In many cases this is enough as even for custom classes used as variables users can implement custom toString() method that produces expected "view" of the variable. 
  
  Though this might not cover all needs, especially when there is a need for efficient queries by variables (both task and process). Let's take as an example a Person object that has following structure:
  
  
  [source,java]
  ----
  public class Person implements Serializable{
  
      private static final long serialVersionUID = -5172443495317321032L;
      private String name;
  
negative.code:   http://java.sun.com/xml/ns/persistence/orm http://java.sun.com/xml/ns/persistence/orm_2_0.xsd"
    xmlns="http://java.sun.com/xml/ns/persistence"
    xmlns:orm="http://java.sun.com/xml/ns/persistence/orm"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  
    <persistence-unit name="org.jbpm.persistence.jpa" transaction-type="JTA">
      <provider>org.hibernate.ejb.HibernatePersistence</provider>
  