-
Type: Bug
-
Status: Resolved
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 5.8
-
Fix Version/s: 5.8.0-HF04, 5.9.1
-
Component/s: Workflow
If this property is not set to null, when looping the second time, some conditions relying on numberOfTasks will be miss-evaluated '.
Eg:
"NodeVariables[\"tasks\"].getNumberEndedWithStatus(\"trans1\") ==1"
A node can't be resumed as long as there are open tasks, so the node can't never be in 'runningInput' and have infos in the taskInfo list that are still needed.