!! This feature may need to be discussed with our client !!
There exist some case in the dummy database that when $TMP/$ID occur, the input parameter $I{num} wont occur separately in the executable command. For example:
and
This may be due to the fact that the previous task had all the input files in the $TMP/$ID directory.
So I currently assume that in such a case, the clt parser will not automatically add the input files to the execution command (which means, it will not automatically generate $I1, $I2, etc. and add to the executable). Unless the user specifies $(input.input_field_name.basename) directly in the arguments field.
!! This feature may need to be discussed with our client !! There exist some case in the dummy database that when
and
This may be due to the fact that the previous task had all the input files in the
$TMP/$IDoccur, the input parameter$I{num}wont occur separately in the executable command. For example:$TMP/$IDdirectory.So I currently assume that in such a case, the clt parser will not automatically add the input files to the execution command (which means, it will not automatically generate
$I1,$I2, etc. and add to theexecutable). Unless the user specifies $(input.input_field_name.basename) directly in the arguments field.