The usual way is to store the outputs from the first workflow to attributes, and then either bind these attributes to the inputs of the second workflow (if they are compatible and you want to use the output value directly as input to the next element), or add a scriptable task element to post-process the output values and compute the values of another attributes to be bound as inputs of the second workflow.
what is there in Powershell Output .. String, integer, object, Vector
Output is string and integer both.
For simple type you can extract them from the output and provide them as input on following actions.
Attaching sample workflow demonstrating how to extract output of type :
- array of numbers
- array of complex objects
Take a look also at sample workflow distributed with the plugin "Library/PowerShell/Samples/List directory content"
For providing complex type object between vRO actions all scrpts must be executed in in same PowerShell session and PowerShellRemotePSObject" must be used as input type in receiving action.
There is more complex example for providing result from one ps script to following using PowerShellRemotePSObject distributed with the plugin (see "Library/Powershell/Samples/Pipeline execution example")
Let me know if you need further details/examples