Hey @MutedJam , thanks for getting back on this.
Sure, sub-workflow is an option, but it’s not always the best alternative (particularly in view of the current UX).
This is a bit disconcerting for me.
Could you please share more as to why one of the core functionalities has been discarded/broken without any suitable alternative?
Because, from my experience and for programming in general, nested loops/foreach are indeed a fundamental entity, regardless of the Development tool being ‘visual-based’/‘low-code’/‘no-code’ etc.
Also, maintaining a repository of ‘old nodes’ doesn’t seem to be a very sustainable choice either. As there’s no official support/maintenance for them beyond a particular release, as well as it’s not really very convenient to maintain a private collection of old nodes.
Sure, will raise a feature request for this.
Although, i’m afraid it will suffer the same fate as another core node, the Function node (Recommendation: allow full-screen(-ish) editor for the Code node).
Best,