This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
bw:executing_a_workflow [2019/10/14 14:24] runger created |
bw:executing_a_workflow [2020/06/05 10:20] (current) akoehler [Scheduled Execution] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ======Executing a Workflow====== | ======Executing a Workflow====== | ||
| - | There are three methods to execute a Bizweaver workflow: test/debug mode, “run now,” and scheduled. The results are the same for all methods. | + | There are four methods to execute a Bizweaver workflow: test/debug mode, “run now", scheduled, and from SQL. The results are the same for all methods. |
| ===== Test/Debug Mode ===== | ===== Test/Debug Mode ===== | ||
| Line 12: | Line 12: | ||
| First, the currently active workflow can be executed by clicking the “Run now” link as shown below. | First, the currently active workflow can be executed by clicking the “Run now” link as shown below. | ||
| - | {{: | + | {{ : |
| Second, right-click on any workflow in the Workflow List area, and select the “Run now” option. | Second, right-click on any workflow in the Workflow List area, and select the “Run now” option. | ||
| Line 22: | Line 22: | ||
| At the end of the execution a “Task Execution Status” window is automatically displayed showing the log information for the workflow. | At the end of the execution a “Task Execution Status” window is automatically displayed showing the log information for the workflow. | ||
| - | {{: | + | {{ : |
| In general, you will only need to scan the log records for information in the “Message” column. These will typically be error messages that may need attention. | In general, you will only need to scan the log records for information in the “Message” column. These will typically be error messages that may need attention. | ||
| Line 32: | Line 32: | ||
| Click the [**Close**] button to close the window. An additional dialog will allow you to delete the log records here as well. | Click the [**Close**] button to close the window. An additional dialog will allow you to delete the log records here as well. | ||
| - | Note that the log records can be retained if desired. This can be helpful if you are doing reporting from the Bizweaver log table. See **//[[bw:application_introduction# | + | Note that the log records can be retained if desired. This can be helpful if you are doing reporting from the Bizweaver log table. See the **//[[bw:actitivity_logging|Acitivty |
| ===== Scheduled Execution ===== | ===== Scheduled Execution ===== | ||
| - | Bizweaver workflows can be automatically executed based on a schedule. This is the most common, and most efficient, way to execute workflows. | + | Bizweaver workflows can be automatically executed based on a schedule |
| + | ===== Call From SQL Server ===== | ||
| + | |||
| + | The process to initiate a Bizweaver workflow from the SQL Server database is described **// | ||
| + | |||
| + | ===== Call From Web Service Tool===== | ||
| + | |||
| + | The process to initiate a Bizweaver workflow from the WebService Tool is described **// | ||