This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
bw2:executing_a_workflow [2023/01/04 14:33] mfoster |
bw2:executing_a_workflow [2024/09/09 13:28] (current) dlee [Executing Workflows from SQL Using Listener-Based Trigger] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ======Executing a Workflow====== | ======Executing a Workflow====== | ||
| - | 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. | + | There are five methods to execute a Bizweaver workflow: test/debug mode, “run now", scheduled, and from SQL via the Bizweaver web service, and from SQL via a trigger. |
| ===== Test/Debug Mode ===== | ===== Test/Debug Mode ===== | ||
| Line 45: | Line 45: | ||
| Bizweaver workflows can be automatically executed based on a schedule using the built-in functionality within Bizweaver. This is the most common and most efficient way to execute workflows. For more details please follow the link, **// | Bizweaver workflows can be automatically executed based on a schedule using the built-in functionality within Bizweaver. This is the most common and most efficient way to execute workflows. For more details please follow the link, **// | ||
| - | ===== Call From SQL Server (SAP Business One) ===== | + | ===== Executing Workflows from SAP Business One ===== |
| - | The process | + | The configuration |
| - | ===== Call From SQL Server (SAP Business One) Using HTTPS ===== | + | ===== Executing Workflows from SQL Using the Bizweaver Web Service |
| - | The process | + | The configuration |
| - | ===== Call From Web Service Tool===== | + | ===== Executing Workflows Using the Web Service Tool===== |
| - | The process | + | The configuration |