Java Edit Variable

Options

Flow Variable List

The list contains the flow variables that are currently available at the node input. Double clicking any of the entries will insert the respective identifier at the current cursor position (replacing the selection, if any).

Snippet text area

Enter your java code here. You can access input flow variables by defining them in the Snippet fields for input. A second way is to use the method getFlowVariable(name, type) where name is the name of the flow variable, respectively. You can use the following values for the type parameter.
tString : String
tInt : Integer
tDouble : Double

Java Snippet Methods:
getFlowVariable(name, type) : Get value of a flow variable by name
getFlowVariables(type) : Get all flow variables by type. A name to value map is returned.
flowVariableExists(name) : Check if a flow variable with given name exists
isFlowVariableOfType(name, type) : Check if a flow variable is of type

You can hit ctrl+space to get an auto completion box with all available classes, methods and fields. When you select a class and hit enter a import statement will be generated if missing.

Note, that the snippet allows defining custom global variables and custom imports.

Exceptions in the snippet are caught by the framework and will cause the execution to fail. If you want to stop execution, please use an exception of class Abort. It gives the user a nice error message.

Input

Define system input fields for the snippet text area. Every field represents a flow variable of the input.

Output

Define flow variables that will be added to stack of flow variables at the output. Every row in the Output table defines a java field bound to a flow variable. Values assigned to this field in the snippet will set the value of the flow variable at the output.

Run script during node configuration or during node execution

In the former case, the snippet is run as soon as the node is configured (default). In the latter case, the snippet is run only once when the node is being executed, i.e. going from yellow to green state. This means that variables are populated later, often causing downstream nodes to be not configurable, as the created variables have a meaningless default value. However, sometimes this is necessary when, for instance, the snippet involves heavy computation, network access or another kind of I/O operation. If unsure, set this option to run the script during node configuration.

Views

This node has no views

Workflows

• 00 Main MenuKNIME Hub
• 00 Main MenuKNIME Hub
• 00_Guided_Labeling_for_Document_Classification_(legacy)KNIME Hub
• 00_Visual_Analysis_of_Sales_Data(2)KNIME Forum
• 00_xplan sf dbconv-insert via xport-AccountKNIME Hub
• Show all 1082 workflows

Links

• KNIME E-Learning Course: Creation and usage of Flow Variables in a KNIME workflow

  www.knime.com/knime-introductory-course/chapter7/section1/creation-and-usage-of-flow-variables
• Loop until previous date is not weekends and holidaysby JanDuo on 2020-08-26

  forum.knime.com/p/100780
• How to open result of workflowby qqilihq on 2018-08-02

  forum.knime.com/p/46080
• Execute failed: Cannot read file “knime_container_20200301_1905559478659870280.bin.snappy”by qqilihq on 2020-03-01

  forum.knime.com/p/83021
• Popup Window in Workflowby qqilihq on 2021-01-29

  forum.knime.com/p/114555
• output the generated data to the console?by qqilihq on 2022-11-12

  forum.knime.com/p/174998
• How to make an useragent loop in a larger loopby qqilihq on 2024-02-15

  forum.knime.com/p/249729
• ETL: custom header and footerby qqilihq on 2020-03-18

  forum.knime.com/p/84680

Developers