- 
    Bug 
- 
    Resolution: Done
- 
    Major 
- 
    None
- 
    None
- 
    None
- 
        2021 Week 40-42 (from Oct 4), 2021 Week 43-45 (from Oct 25)
- 
        3
- 
        NEW
- 
        NEW
Attached Scenario
The MID takes a list of names.
Inside of the MID, for each name, we first calculate the length of the name string, then multiply it by 2.
In the end, we sum up all the results from the MID.
Example: Input is a list ["John", "Alice"], and expected result would be (4*2) + (5*2) = 18
Actual Behavior
An error is logged, showing that the middle-level decision inside of the MID ("toNumber") cannot access the iterator variable.
Ideas
We've tried to debug a bit already, but didn't find a definitive solution.
An error we encountered was that the MID can be compiled before it's inner decisions. If this happens, then we don't know the dependencies of the inner decisions yet. So the getDependencies() inside of recurseNodeToRemoveItAndDepsFromModelIndex returns an empty collection, which means the middle-level decision will not be removed from the model index.
Still, when we manually moved the MID to the bottom of the XML, we could watch the middle-level decision be removed, and we still encountered the error.
- relates to
- 
                    DROOLS-5711 [DMN XML] Signavio Profile - MultiInstanceDecisionLogic: MID requirements are not linked -         
- Closed
 
-