"Workflow Executor" node suggestion

[aworker]

Hi @HaveF

Thanks for clarifying and for posting your workflow.

Definitely I was missing the point because you are using the -Workflow Executor- node and I was thinking of the -Call Local Workflow- node which has the behaviour I mentioned. You are completely right about the behaviour of the former.

I was biased towards the -Call Local Workflow- node when reading your post because recently I posted the following solution:

Better alternative to CASE SWITCH (with 15 options)?

Hi @kowisoft Sorry I’m replying late to your posts and questions about the JSON implementation since it is only now I have access to a computer with KNIME. The good news is that you got the idea and managed to implement it eventually ! I had a look at your solution and it could be implemented in a simpler way just by using the -Call Local Workflow (Table Based)- and the -Container Input (Table)- nodes. I do not think one needs the JSON versions in your case although it is a very good e…

which is very similar to what you are doing but based on the -Call Local Workflow- node in case you would like to have a look at it as an alternative to call external workflows.

Best
Ael