Yes, it might be interesting with native support but for now you can execute PowerShell scripts just the way you execute Perl, PHP and other script languages with scripting engines.

What you need to do is to point out the engine as command, in this case something like:

C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

Then use your PowerShell command as argument like:

Get-Process

write-host "Process files..."

$Files = get-childitem $FilePath | where-object {$_.name -like "*foobarfiles*"}

foreach ($file in $Files)
{
  if ($file -ne $NULL)
  {
    $filetoProcess = $FilePath + $file
    & $Admin /FILE:"$filetoProcess"
    $filetoProcess | move-item -destination $OutputPath
  }
}

Thanks for the sample.

The problem is that PowerShell seems to handle the working directory very differently. The problem is that it does not find any files in whatever folder it is looking at. So, you have to options:

1. find a way to set this working directory or hard code directory to search in in some other way

2. check "Use shell execute" option in Execute settings. The disadvantage with this is that you won't get the output.

1. I don't know why but that does not work. It does not find the files. I don't know which function fails internally within PowerShell but it does not find any files and because of that it does not work unless you do the workarounds.


2. Maybe because you have not specified the full path to the script? The script worked for me.

Did you try to check "Use shell execute"?

What if you use "Use shell execute" and remove the Credential?