Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-8460

Multi instance activity doesn't support completionCondition correctly

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Trivial
    • None
    • 7.21.0.Final
    • Runtime Engine
    • None
    • NEW
    • NEW
    • Hide

      Simple bpmn2 with Start Node, Human Task and End Node.

      If HumanTask has multiInstanceLoopCharacteristics with Input Collection specified, Output Collection specified and completionCondition specified

      At runtime, when che condition is met , occurs a NPE

      Show
      Simple bpmn2 with Start Node, Human Task and End Node. If HumanTask has multiInstanceLoopCharacteristics with Input Collection specified, Output Collection specified and completionCondition specified At runtime, when che condition is met , occurs a NPE

    Description

      If completionCondition is specified in the multiInstanceLoopCharacteristics for task (ex. Human Task) , the class ForEachNodeInstance cause NPE

      The class ForEachNodeInstance manage the runtime check of the completionCondition.

      if the completioinCondition is met at this line:

      if (getNodeInstanceContainer().getNodeInstances().size() == 1 || isCompletionConditionMet) {

      the code reach NPE because the local variable subprocessVariableScopeInstance is null if the ForEachNode is applied to task and not subprocess

      Attachments

        Activity

          People

            swiderski.maciej Maciej Swiderski (Inactive)
            paolo.cappuccini Paolo Cappuccini (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: