I suppose you are using the official PowerShell plugin.
In this case Yes it is,
You can use the PowerShell:PowerShellRemotePSObject type to preserve the output from PowerShell sript invocation and to pass it from one scripting box to another. One important not is that you will be able to use the output as long as your powershell session is not closed.
Basicly the steps to follow are:
1. Open PowerShell session (You can use the com.vmware.library.powershell.openSession action)
2. Invoke PowerShell script and preserve the result in attribute of type PowerShell:PowerShellRemotePSObject.
3. Use the attribute as input to some other scripting blocks.
4. close PowerShell session (You can use the com.vmware.library.powershell.closeSession action)
If you are using the scripting API to invoke PowerShell script the steps for getting the output are.
....
var oSession = host.getSession(sessionId)
var result = oSession.invokeScript('$a = "Hello"; $a ');
var output = result.getResults();
...
where :
host - is of type PowerShellHost
oSession - is of type PowerShellSession
result - is of type PowerShellInvocationResult
output - is of type PowerShellRemotePSObject
There is a sample workflow "Toggle virtual machine state" in "Library/PowerShell/Samples" folder that actually passes output from PowerShell script to another scriptiong box..
What actually happens there is.
1. GetVm returns a VM by it's name using pregenerated PowerShell action.
2. The output is than preserved in attribute curVM attribute (of type PowerShellRemotePSObject)
3. poweredOff decision block is invoked recieving as parameter curVM attribute.
4. Based on the state of the curVM another powershell action is invoked (stopVm or StartVM ).
