This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
bw2:wfexec_tool [2020/12/15 13:53] akoehler created |
bw2:wfexec_tool [2024/01/03 16:06] (current) wgates [Executing A Bizweaver Workflow] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ======WF_Exec | + | ======Exec Tool===== |
| The **WF_Exec** tool allows an external batch file (most common) or program (.exe) to be executed via a workflow step. The most common use of the tool is to execute a batch file that, in turn, executes **// | The **WF_Exec** tool allows an external batch file (most common) or program (.exe) to be executed via a workflow step. The most common use of the tool is to execute a batch file that, in turn, executes **// | ||
| Line 7: | Line 7: | ||
| The **Run** tab is used to execute an external batch file or program. | The **Run** tab is used to execute an external batch file or program. | ||
| - | {{ :bw:wftool_exec1.png? | + | {{ :bw2:bizweaverexectool1.png |}} |
| * Select (or enter) the full path to the batch file or program file to be executed. | * Select (or enter) the full path to the batch file or program file to be executed. | ||
| * Enter any arguments (parameters) to be passed to the process being executed. | * Enter any arguments (parameters) to be passed to the process being executed. | ||
| Line 20: | Line 20: | ||
| The **Other Functions** tab can be used to start, stop, and restart Windows services. | The **Other Functions** tab can be used to start, stop, and restart Windows services. | ||
| - | {{ :bw:wftool_exec2.png? | + | {{ :bw2:bizweaverexectool2.png |}} |
| * Enter the name of the service to be affected. | * Enter the name of the service to be affected. | ||
| Line 27: | Line 27: | ||
| The **WF_Exec** Tool can also be used to call Bizweaver workflows. This process is normally handled by the **// | The **WF_Exec** Tool can also be used to call Bizweaver workflows. This process is normally handled by the **// | ||
| - | {{ ::execcallingbwworkflow.png? | + | {{ :bw2:bizweaverexectool3.png |}} |
| * **Full Path**: This is the path to where Bizweaver Commander was installed. | * **Full Path**: This is the path to where Bizweaver Commander was installed. | ||
| Line 33: | Line 33: | ||
| * **Add arguments**: | * **Add arguments**: | ||
| * ExecuteTask_NN where NN is the workflow ID | * ExecuteTask_NN where NN is the workflow ID | ||
| + | * Add a space to add variables to be sent to the workflow to be executed | ||
| + | * If sending multiple variables add a space for each one | ||
| + | * the receiving workflow should have the variables in lowercase of arg1,arg2, etc adding a number for every subsequent variable to be passed. | ||
| + | *<WRAP round tip 70%> | ||
| + | Check the official documentation of the specific software or application you are interested in. Many developers provide detailed information on command-line options and arguments. | ||
| + | </ | ||
| + | ====Execute Variables==== | ||
| + | |||
| + | ^Name ^Description^ | ||
| + | |Arguments|This indicates if there are any arguments that are being passed into an application| | ||
| + | |FullPath|This indicates the full path of the application or file you are accessing| | ||
| + | |FunctionType|This indicates what the application is doing (Run for run tab and Functions for Function tab )| | ||
| + | |WaitForExit|True or False if the wait for exit checkbox is selected| | ||
| + | |StepMessage|During a failure the reason for failure will be populated here| | ||
| + | |StepStatus|True or False| | ||