Kent West
My feedback
-
304 votes
Powershell support for SMA online scripting is targetted for a 2020 release.
-
1 vote
Kent West shared this idea ·
-
1 vote
Kent West supported this idea ·
Make online scripting even more general:
On the online script page, have radio buttons (or a pull-down), with the following options:
* This is a batch script
* This is a Powershell script
* This is a bash script
* This is a python script
* This is a Ruby script
* This is a VB script
* Let the OS figure out the type of script, based on the file extension
There can be a disclaimer that the appropriate interpreter/engine be on the target first. The radio-buttons might even have a field next to them to specify the path to the interpreter/engine on the target machine. Just having this field alone might eliminate the need for the radio buttons:
Path to language engine/interpreter: %winapppath%\python\python3.7
or
Path to language engine/interpreter: {built-in batch interpreter}
or
Path to language engine/interpreter: %windir%\sysnative\ruby
or
Path to language engine/interpreter: {built-in VBS interpreter}
etc
In essence, the "Script Text" field would just become a mini-editor for all sorts of language engines, instead of just batch or shell as it essentially is now.