The following table describes the parameters of the Scripting Node.

Scripting Node parameters

Parameter

Definition

Path to Executable

Specifies the path to an arbitrary command line executable that is started as the workflow execution reaches the Scripting Node.

Users of integrated development environments (IDEs) for R or Python should run their scripts using the corresponding command line tool, i.e., RScript.exe or python.exe.

If a compiled executable program is to be used, the full path of that executable should be selected.

Command Line Arguments

The parameter should include all arguments that need to be passed directly to the executable. If using a scripting language, in general the name of the script to be executed will be the first command line argument. The path to the node_args.json file written by the Scripting Node can be inserted into the command line using the placeholder %NODEARGS%.

This file will be written into the scratch directory. More information about the structure of the node_args.json file is discussed below.

If more parameters past %NODEARGS% are specified, see Reading the node_args.json file into the script.

Requested Tables and Columns

Specifies the requested data tables and columns for the executable using the form: TableName1: Column1, Column2; TableName2: Column3, Column4.... Use the edit button to edit the definition in a multi line text editor. Then, each line starts a new table export definition.

Use R-Friendly Columns

Specifies whether column names are R-Friendly. If set to True, column names are exported in a format that is more readily used by scripting languages such as R. That is, characters such as ", ", #, %, [], or / are removed from the column header string altogether or replaced by alphanumeric text.

Archive Datafiles

If set to True, a zip file is created in the study folder with all files used by the Scripting Node. The zip file includes the node_args.json file and the various text files with the exported columns. This option is useful when debugging a script, and the exported results from the application can be used for other purposes.

If results are being read back into the application for display, all of the text files containing information are archived as well as the node_response.json file.