0 ×

Call Local Workflow (Row Based)

KNIME Nodes for the KNIME Explorer version 3.7.0.v201808081048 by KNIME AG, Zurich, Switzerland

This node can be used to call other workflows in in your local workspace. Input data can be passed to Quickform Input nodes (only the new input nodes, e.g Container Input (JSON)) in the other workflow and results can likewise be read back as a JSON value from JSON Output nodes(e.g Container Output (JSON)). The input can either be a static JSON values provided via the dialog (which itself can be overridden by a flow variable) or from a JSON column in the input table. The node will call the other workflow with every row of the input table and append the results of the call to it.
Note that the workflow you are calling must not be opened in an editor in your workbench and that the workflow can not be executed in parallel. This means that multiple Call Local Workflow nodes using the same called workflow will execute sequentially.

Options

Workflow path: The path to the workflow you want to call. The path can either be absolute to the local workspace if it starts with a slash or relative to the current workflow if it does not start with slash. You can also use paths relative to the current workflow, e.g ../Called Workflow. You may also use an URL with the knime-protocol pointing to a local resource (e.g. knime://TeamspaceMount/Workflow).
Create Report: If checked the report associated with the called workflow will be generated and put into the output table. The format can be chosen in the drop-down. The output table will contain a column containing the binary content of the report (column type: binary object); the column can be further processed, e.g. use a "Binary Objects to Files" node to write the content to a file, or use a database writer to write the report as BLOB into a database. Failures to generate the report (for instance, because no report is attached to the workflow) will result in a missing cell.
Use Fully Qualified Name for Input and Output Parameters: If checked, use the full parameter name to select the input and output. The parameter names are defined by the user in the configuration dialog of each of the parameters (like JSON In/Output node), e.g. "timeout", "count", etc. Using these 'simple names' may lead to duplicates, hence a 'fully qualified name' is constructed by appending a suffix, e.g. "timeout-1" or "count-5:6". While these suffixes guarantee unique parameter names across one workflow they may cause names not to match in case you call out to different workflows (e.g. in a loop). It's good practice to (manually) ensure that parameter names in the called workflow are unique and hence often the 'simple name' is sufficient (= do not check the box).
Inputs: After you have loaded the input format you will see an input block for every input node in the called workflow. You can select if you want to use a static value or the value of a column for the respective input field or use the default value (that is the value that is set up in the workflow being called).

Input Ports

: Any input, possibly with JSON column.

Output Ports

: Output of workflow call

Best Friends (Incoming)

Table to JSON (16 %) Manipulator
Table Creator (14 %) Source
Call Local Workflow (Row Based) (12 %) Other
Empty Table Creator (8 %) Source
Table Row to Variable (4 %) Other
String to JSON (4 %) ManipulatorStreamable
Try (Data Ports) (2 %) ScopeStart
Table Row To Variable Loop Start (2 %) LoopStart
Variable to Table Row (2 %) Other
Database Reader (2 %) Source
Loop End (2 %) LoopEnd
Chunk Loop Start (2 %) LoopStart
Column Filter (2 %) ManipulatorStreamable
Joiner (2 %) Manipulator
String Manipulation (2 %) ManipulatorStreamable
String Manipulation (Variable) (2 %) Manipulator
IF Switch (2 %) Manipulator
Columns to JSON (2 %) ManipulatorStreamable
Download (1 %) Other
Wait... (1 %) Manipulator
File Reader (1 %) SourceStreamable
Table Writer (1 %) Sink
Java Snippet (1 %) ManipulatorStreamable
Generic Loop Start (1 %) LoopStart
Recursive Loop Start (1 %) LoopStart
Column Appender (1 %) ManipulatorStreamable
Cross Joiner (1 %) ManipulatorStreamable
GroupBy (1 %) Manipulator
Empty Table Switch (1 %) Manipulator
Data Generator (1 %) SourceStreamable
Timer Info (1 %) Sink
Excel Reader (XLS) (1 %) SourceStreamable
Term To String (1 %) Manipulator
Boolean Input (1 %) QuickForm
Container Input (JSON) (1 %) QuickForm
JSON Writer (1 %) Sink
~~Flow Variable IF Switch (Flow Variable Value)~~ (< 1 %) ManipulatorDeprecated
Variable to Table Column (< 1 %) OtherStreamable
CSV Reader (< 1 %) Source
List Files (< 1 %) Source
Table Reader (< 1 %) SourceStreamable
Counting Loop Start (< 1 %) LoopStart
Interval Loop Start (< 1 %) LoopStart
Extract Column Header (< 1 %) Manipulator
Constant Value Column (< 1 %) ManipulatorStreamable
Create Table Structure (< 1 %) Source
Column Rename (< 1 %) ManipulatorStreamable
Transpose (< 1 %) Manipulator
Renderer to Image (< 1 %) Other
Rule Engine (< 1 %) PredictorStreamable
SDF Reader (< 1 %) Source
External Tool (< 1 %) Other
String Input (< 1 %) QuickForm
~~Python Script (2⇒1)~~ (< 1 %) ManipulatorDeprecated
Show all 54 recommendations

Workflows

Installation

To use this node in KNIME, install KNIME Nodes for the KNIME Explorer from the following update site:

Drag me!

Wait a sec! You want to explore and install nodes even faster? We highly recommend our NodePit for KNIME extension for your KNIME Analytics Platform.