...

• Consider that node arguments cannot be modified dynamically - which is why they are called arguments, not variables. 
• Node arguments are available for mapping to environment variables in a similar manner to order variables.

Creating Order Variables

Order variables can be created dynamically from shell jobs.

• The job script can append a pair of name and value for a variable to a temporary file indicated with the $JS7_RETURN_VALUES environment variable.
• The JS7 Agent will pick up the temporary file after execution of the shell job and from the file's entries will create new order variables for subsequent instructions and jobs in the workflow.
• This mechanism is used to create new order variables from Shell Jobs. It cannot be used to modify existing order variables. Shell jobs always should create new order variables to pass values to subsequent instructions and jobs.

SOME_VARIABLE="some value"
echo "myVar=$SOME_VARIABLE" >> $JS7_RETURN_VALUES

set SOME_VARIABLE=some value
echo "myVar=%SOME_VARIABLE%" >> %JS7_RETURN_VALUES%

Explanation:

• Both examples assign some value to an environment variable SOME_VARIABLE that is local to the job.
• The name/value pair myVar=.... is appended to the temporary file indicated by the JS7_RETURN_VALUES environment variable.
  • This assignment makes use of the value stored with the SOME_VARIABLE environment variable.
  • This assignment could use a constant value too instead of using SOME_VARIABLE.

Built-in Variables

Built-in variables are available at the following scopes:

...