anchor.diff:  
   A milestone is used to mark arriving at a certain point in the case instance. At runtime, they are represented as *MilestoneInstances* and they can be queried through the *MilestoneInstanceQuery* via the _CmmnRuntimeService_. There is also a historical counterpart via the _CmmnHistoryService_.
   
  -A milestone is a plan item, which means that beyond a milestone entry aso a _PlanItemInstance_ is created and it can be queried via the _PlanItemInstanceQuery_.
  +A milestone is a plan item, which means that as well as a milestone entry, a _PlanItemInstance_ is created also, which can be queried via the _PlanItemInstanceQuery_.
   
   
   Properties:
   
  -* *name*: an expression or static text that determines the name of the mile stone.
  -
  -A milestone is visualized as a rounded rectangle with, slightly more rounded than a task:
  +* *name*: an expression or static text that determines the name of the milestone
  +
  +A milestone is visualized as a rounded rectangle (more rounded than a task):
   
   image::images/cmmn.milestone.png[align="center"]
   
  
positive.code: </dependency>
  ----
  
  All case variables that are accessible through the PlanItem instance that arrives in the script task can be used within the script. In the example, the script variable _'inputArray'_ is in fact a case variable (an array of integers).
  
  [source,xml,linenums]
  ----
  
negative.code: 
  Exit criteria form a sentry for a given plan item instance. They consist of two parts:
  
  * One or more parts that depend on other plan items: these define dependencies on state transitions of other plan items. For example, one human task can depend on reaching a certain milestone to be automatically terminated
  * One optional _if part_ or _condition_: this is an expression that allows a complex condition to be defined
  
  A sentry is satisfied when all its criteria are resolved to _true_. When a criterion evaluates to true, this is stored and remembered for future evaluations. Note that exit criteria of all plan item instances in the _active_ state are evaluated whenever something changes in the case instance.
  
  Multiple sentries are possible on a plan item. However, when one is satisfied, the plan item moves from state _active_ to _exit_.
  
  An exit criterion is visualized as a diamond shape (white color inside) on the border of a plan item:
  
  image::images/cmmn.exitcriteria.png[align="center"]
  
  