Call the workflow table based on the variable that does not accept with the path

[mlauber71]

@cridiaz I reworked some of the workflows and updated to the new call workflow environment. This now seems to be easier to understand. You configure a sub-workflow with inputs and outputs and then you point the main-workflow to the sub-workflow and apply the settings so magically the input and output ports will appear like in the sub-workflow. And I think you can then work with them.

Another example just stores data locally and then loads them in the sub-workflow but maybe that is not so elegant.

use data from another workflow into current workflow

@sanderlenselink you can call a KNIME workflow from another one and transfer data to that workflow: What you want to keep in mind is that you will have to make sure what data is created when and do you have the relevant status. KNIME does that via Flow Variables and Workflow orchestration. I would suggest to combine the approaches. Transfering data via KNIME table should be stable:

There is another framework where you can execute something like a compacted workflow called “Integrated Deployment”:

https://docs.knime.com/latest/integrated_deployment_guide/index.html#introduction

parent – armingrudd