anchor.diff:  void removeTransientVariableLocal(String variableName);
   ----
   
  -Following BPMN diagram shows a typical example:
  +The following BPMN diagram shows a typical example:
   
   image::images/api.transient.variable.example.png[align="center"]
   
  -Let's assume the 'Fetch Data' service task calls some remote service (for example using REST). Let's also assume some config parameters are needed and need to be provided when starting the process instance. Also, these config parameters are not important for historical audit purposes, so we pass them as transient variables:
  +Let's assume the 'Fetch Data' service task calls some remote service (for example, using REST). Let's also assume some configuration parameters are needed and need to be provided when starting the process instance. Also, these configuration parameters are not important for historical audit purposes, so we pass them as transient variables:
   
   [source,java,linenums]
   ----
  
positive.code: }
  ----
  
  The +contextInitialized+ method will delegate to +ProcessEngines.init()+. That will look for +flowable.cfg.xml+ resource files on the classpath, and create a +ProcessEngine+ for the given configurations (e.g. multiple jars with a configuration file). If you have multiple such resource files on the classpath, make sure they all have different names. When the process engine is needed, it can be fetched using
  
  [source,java,linenums]
  ----
  
negative.code:     .list();
  ----
  
  Sometimes you need more powerful queries, for example, queries using an OR operator or restrictions you cannot express using the Query API. For these cases, we have native queries, which allow you to write your own SQL queries. The return type is defined by the Query object you use and the data is mapped into the correct objects (Task, ProcessInstance, Execution, ...). Since the query will be fired at the database you have to use table and column names as they are defined in the database; this requires some knowledge about the internal data structure and it is recommended to use native queries with care. The table names can be retrieved through the API to keep the dependency as small as possible.
  
  [source,java,linenums]
  ----
  