commandexecutordocumentation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
commandexecutordocumentation [2022/01/09 19:33]
wikiadmin 		commandexecutordocumentation [2022/01/09 21:02] (current)
wikiadmin
Line 15: Line 15:
 The Output of this Bean is the text which would be generated if the command were executed in a command shell or terminal. The Output of this Bean is the text which would be generated if the command were executed in a command shell or terminal.
  
-===Examples===+===Run a Simple Command===
  
 <note important>For Windows, you must run the "cmd /c" command shell to execute a command. The "/c" ensures that the process returns and terminates after completion, or it will appear to hang.</note> <note important>For Windows, you must run the "cmd /c" command shell to execute a command. The "/c" ensures that the process returns and terminates after completion, or it will appear to hang.</note>
Line 33: Line 33:
 </code> </code>
  
 +===Running a .sh or .bat===
  
-===Using in a Script===+You can use the Command Executor to run a Linux .sh or Windows .bat. Example commands for Linux and Windows are:
  
 +<code text>
 + ./reports/run_report.sh
 +</code>
 +
 +<code text>
 +cmd /c start  .\\reports\\run_report.bat 
 +</code>
 +
 +===Passing Parameters===
 +
 +An Array Value Object can be constructed (either by script or using a StringToArray, for example) and passed into the "Argument Input" trigger of the CommandExecutor. The AVO will trigger the command set in the "Command" property with the elements of the array on the command line in order that they were added to the AVO.
  
 ===Configuration=== ===Configuration===
  • commandexecutordocumentation.1641778414.txt.gz
  • Last modified: 2022/01/09 19:33
  • by wikiadmin