syscmd node: Capturing Data From PowerShell Script To Be Processed By Other IPA Nodes

We are testing a flow in which a 'syscmd' node executes a PowerShell script to process data files and then extract values from a logfile. These values will be used by other nodes in the flow to determine what actions should be taken. Currently, the "Return" command is being used to pass the data back to the 'syscmd' node. When the developer reviews the variables associated with the 'syscmd' node, the OutputData variable contains all the information that was written by the script's 'Write-Host' commands, as well as the value passed by the 'Return' command at the end of the dialog.

What is the best solution that will allow the information written by the 'Write-Host' commands to still be visible, but allow the data passed by the 'Return' command to be saved into a variable that can be used by other nodes in the flow?

Find more posts tagged with

Process Automation (IPA) - General Discussions

Comments

unknown

It depends at bit on the data coming back. If the Return data will always be the same length then something like OutputData.slice(-4) to capture the last 4 characters of the string. JavaScript has several methods that could work depending on your needs (other examples - split, substr, substring).

russel-cornelson

Good afternoon Michael,
The system command can only grab output data from the script you are calling, so you will need to work within that constraint.

Kyle's suggestion would be what I would do; before the return I would Write-Host "~"

Assign node after system command; var [writehostdata,returndata] = SysCmd_outputData.split("~")
NOTE: Assuming output data is a string here; if it fails create "sysout" in start node as a string. Then before javascript in assign node sysout = SysCmd_outputData and split on the sysout instead.

Alternatively change Write-Host to within the flow to use a Log file and have the flow read in the log file after powershell is done executing.

Example ps1
param([string]$workunit) [tag:accepts] a parameter from ps command line

$LogFile = ("D:ProcessFlowLogs" + $workunit + ".log"
$returnString = "ReturnResultOnCompletion"

Function LogEntry{
param([string]$entry)
$Date = Get-Date
$DateString = $Date.ToShortDateString()
$TimeString = $Date.ToShortTimeString()

Add-Content $LogFile "$DateString - $TimeString ------ $entry"
}

LogEntry ("Start of Script Execution ...")
... rest of script here
Return $returnString

Then when you call the powershell script you could just powershell.exe .example.ps1 <!WorkUnit>
This would create a log file with the name of the log being your workunit# so other workunits don't overwrite it.

Copyright © 2025 Infor. All rights reserved.