<div dir="ltr">G'day again,<div><br></div><div>After sending the initial mail it occurred to me I could test my theory by directly starting the first level Subflow directly, and as guessed the subsequent parallel subflow step initiates successfully. So I'm guessing there is a limitation (potentially a bug in release Basis 731 sp 16) that means you can't have a parallel subflow within a parallel subflow. I get that there could be concerns for endless loops spawning recursive subflows but seems a bit rude to not support it at all. </div><div><br></div><div>In the screen shot below you can see when I started an instance of the subflow WS90100016 that it successfully spawned an instance of WS90100019 in step 1396. No changes to bindings or data, just this time WS90100016 wasn't a subflow. </div><div><br></div><div><img src="cid:ii_jfl2slqt0_16290a7c9a73a28f" width="472" height="209"><br><br></div><div>Anyone know if it should ever work or am I just pushing the boundaries of the sane? </div><div><br></div><div>Have fun,</div><div>Mark</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 4 April 2018 at 19:06, Mark Pyc <span dir="ltr"><<a href="mailto:mark.pyc@gmail.com" target="_blank">mark.pyc@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">G'day Wuggers,<div><br></div><div>Wow, been a long time, but scratching my head again so once again come to the fount of all WF knowledge.</div><div><br></div><div>I'm helping another developer who has got to a point of confusion in a parked Logistics Inv. scenario where an Invoice is Held with reference to multiple POs and multiple items within those POs. It is Saved as Held as there are no Service Entry Sheets. The solution is to send create parallel WFs out per PO to the PO creator/requestor asking them to create Service Entry Sheets (SES) if appropriate. The desire is to have a Wait for Correlated Event that an SES has been created for each item. You can't seem to create parallel Wait for Correlated Event steps, so have put the Waits inside a Subflow.</div><div><br></div><div>The binding to the Sub-Subflow is based on &PO_ITEMS[&_WF_PARFOREACH_<wbr>INDEX&]& with the Items table indicated on the Misc tab. </div><div><br></div><div>The system doesn't throw an error, but it doesn't create the subflow either. In the log there is a phantom step with a step type of "STEP" which I can't ever remember seeing before. Note that although there is a Node number there is no Task Number and no Workitem Number</div><div><img src="cid:ii_jfkv4ryt0_1628fe3723908867" width="454" height="164"></div><div><br></div><div>Is this some weird restriction that you can't have a parallel subflow within a parallel subflow??? </div><div><br></div><div>The WF just carries on like that Step doesn't exist, which indeed it doesn't seem to. </div><div><br></div><div>I'm not justifying the design either from a business process or technical build, but I'm at a loss as to what is happening technically when trying to implement this. </div><div><br></div><div>Appreciate any sagely input!</div><div><br></div><div>Have fun,</div><div>Mark<br><br></div><div><br></div></div>
</blockquote></div><br></div>