This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
bizweaver:exec_tool [2024/09/09 13:18] dlee created |
bizweaver:exec_tool [2024/09/09 13:24] (current) dlee |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ======Called from another Workflow====== | ======Called from another Workflow====== | ||
| - | To execute another workflow within Bizweaver, use a **// | + | To execute another workflow within Bizweaver, use a **WebService2** step. The step is configured to use POST. When the second workflow is called, the calling workflow will wait until it receives a response from the called workflow. Once a response is received, the calling workflow will continue to its next step. |
| - | <WRAP center round tip 80%> | ||
| - | Processes beginning with v2.4 should always use POST. Processes from older versions that used GET should be converted to POST as soon as possible. | ||
| - | </ | ||
| <WRAP center round important 80%> | <WRAP center round important 80%> | ||
| - | A token must be generated in order to use the POST processes described below. | + | A token must be generated in order to use the POST processes described below. |
| </ | </ | ||
| <WRAP center round important 80%> | <WRAP center round important 80%> | ||
| Line 14: | Line 12: | ||
| - | =====Call Another Workflow Using POST===== | + | =====WebService2 Tool Setup===== |
| When a Bizweaver workflow is called (initiated) using POST, the configuration of the WebService2 tool involves two sections: the URI and the Body. An example is shown below. | When a Bizweaver workflow is called (initiated) using POST, the configuration of the WebService2 tool involves two sections: the URI and the Body. An example is shown below. | ||
| {{ : | {{ : | ||
| - | |||