3468392 - What is the logic behind the AppendAll function?

Within our Decision Models, we will be outputting several IDs in each decision table. At the end of the model, we need to take the outputs of each decision and append them all in to one ‘Final Requirements’ list. We encounter conflicting experiences when trying to use the AppendAll function when combining these lists (“Scenario A” & “Scenario B”).

In Scenario A, we take the outputs of 4 decision tables at a time and appended them together, before appending the outputs of these sub-decisions into a ‘Final Requirements’ decision. When appending in this way, the following simulation error occurs: "In the decision Final Requirements, the parameters of a function call do not have the same enumeration type."

In Scenario B, we take the outputs of the first 2 decision tables and appended them together, then took the output, and appended with the next decision table down. This is repeated until all decision tables were included. When appending this way, it's possible to simulate without errors. What is the logic behind the AppendAll function?

AppendAll, FEEL, DMN, SPM, function, decision table, output, append, logic , KBA , BPI-SIG-PM-SET-MOG , Modeling Guidelines for SAP Signavio Process Manager , BPI-SIG-PM-MOD-SIM , Simulation for SAP Signavio Process Manager , Problem