Hello,

We need to launch Powershell script with arguments, but I'm not able to pass arguments on Powershell Task Type

It is possible to add an arguments field like "Execute" tasks on "Powershell" tasks ?

thanks

Ok, that should not be a problem adding.

---

It would be sweet if we can add a visualcron variables as parameters after the called script as a powershell script file. Such as below:

C:\scripts\powershellscript.ps1 {TRIGGER(Active,LastTrigger,File.Result.Name)} {TASK(bc897f8e-492a-4b82-a591-1eff3be8534e,StdOut)}


Or embedded in a powershell script text:
$triggerfile = {TRIGGER(Active,LastTrigger,File.Result.Name)}
$releasestring = {TASK(bc897f8e-492a-4b82-a591-1eff3be8534e,StdOut)}

Hi Steve

That already works (embedded variables). I run PoSH scripts like this:

$prof = "{USERVAR(@DPrf)}"
$docdef = "{USERVAR(@DocDef)}"
$inpfil = "{USERVAR(@Infile)}"
$outfil = "{USERVAR(@ClientRoot)}\vctestdflt.AFP"
$logfile = "{USERVAR(@ActLog)}"
#$logfile = "C:\@VC\log\powershell.lint"
$exe = "c:\isis_v72\pdew3700\pdew3.exe"

$prjstr = "/compile /profile=$prof /docdef=$docdef /input=$inpfil"

$a = "$exe $prjstr"

Invoke-Expression $a | Out-File $logfile


Cheers

Andy

We have now implemented parameter support in the PowerShell Task. Will be presented in the next version.

---

What I've been doing when I needed this is using the powershell script box and dot-sourcing my script. Well, actually, in those cases, I write a function in the script, dot-source it, and then call it, rather than giving the script parameters directly.

What I've been doing when I needed this is using the powershell script box and dot-sourcing my script. Well, actually, in those cases, I write a function in the script, dot-source it, and then call it, rather than giving the script parameters directly.

Yes, I know about the workaround, and I think that is a good alternative. But this might be more straight forward for some users, especially for those who do not want to touch their scripts.

---