Search before asking
What happened
I first tested with two Shell nodes:
In node1, I set an output parameter as a custom parameter with direction out, and executed echo '${setValue(output=123)}' in the script to assign a value to it.
In node2, I executed echo ${output} and set node1 as its upstream task.
when I added a custom parameter named output (direction in) to node2, node2 could print the parameter value normally.
However, it could NOT retrieve the output value when I modified node1 to a Stored Procedure node.
I set output as the output value of the upstream Stored Procedure node (node1).it could NOT retrieve the output value.
Node1 configuration:
Node2 configuration
It seems node1 successfully retrieved the return value: return123.
But node2 output was empty.
I tested the exact same operations in version 3.2.2, and there were NO such issues.
I followed the parameter passing section in the official documentation for version 3.4.0, so the syntax should be correct.
What you expected to happen
Local parameter passing of Procedure to Shell not working in version 3.4.0
It seems node1 successfully retrieved the return value: return123.
But node2 output was empty.
How to reproduce
Node1 configuration
Node2 configuration
Node1 return value
node2 output
Anything else
No response
Version
3.4.0
Are you willing to submit PR?
Code of Conduct
Search before asking
What happened
I first tested with two Shell nodes:
In node1, I set an output parameter as a custom parameter with direction out, and executed echo '${setValue(output=123)}' in the script to assign a value to it.
In node2, I executed echo ${output} and set node1 as its upstream task.
when I added a custom parameter named output (direction in) to node2, node2 could print the parameter value normally.
However, it could NOT retrieve the output value when I modified node1 to a Stored Procedure node.
I set output as the output value of the upstream Stored Procedure node (node1).it could NOT retrieve the output value.
Node1 configuration:
Node2 configuration
It seems node1 successfully retrieved the return value: return123.
But node2 output was empty.
I tested the exact same operations in version 3.2.2, and there were NO such issues.
I followed the parameter passing section in the official documentation for version 3.4.0, so the syntax should be correct.
What you expected to happen
Local parameter passing of Procedure to Shell not working in version 3.4.0
It seems node1 successfully retrieved the return value: return123.
But node2 output was empty.
How to reproduce
Node1 configuration
Node2 configuration
Node1 return value
node2 output
Anything else
No response
Version
3.4.0
Are you willing to submit PR?
Code of Conduct