Align RepetitionRule implementation with CMMN 1.1 specification

AT:

• delete repetition criterion
• delete properties CaseExecution#repeatable and CaseExecution#repetition
• align with CMMN 1.1 specification:
  • if the activity has at least one entry criterion, then the repetition rule is evaluated in the transition enable or start (depending on ManualActivationRule). If the repetition rule evaluates to true, a new instance is created.
  • if the activity has not any entry criterion, then the repetition rule is evaluated in the transition complete or terminate. If the repetition rule evaluates to true, a new instance is created. (Note: the repetition rule is not evaluated in the transition create)
  • if the activity has not any entry criterion and the repetition rule contains a Camunda custom property named repeatOnStandardEvent, then the repetition rule is evaluated in the declared transition. In the following example the repetition rule is always evaluated in the transition disable. So whenever the task transitions into the state disabled the rule is evaluated and if it is true, then a new instance of task is created:

      <planItem definitionRef="HumanTask" id="PI_HumanTask" />
      <humanTask id="HumanTask">
        <defaultControl>
          <repetitionRule camunda:repeatOnStandardEvent="disable">
            <condition>${anyExpression}</condition>
          </repetitionRule>
        </defaultControl>
      </humanTask
    

  • the result of the repetition rule is not persistent