Table of Contents
Called from another Workflow
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.
A token must be generated in order to use the POST processes described below. The token can be generated from the Setting page.
Use caution when connecting multiple workflows in a sequence. You may need to adjust the timeout value on the earlier steps to ensure the processing doesn't continue before the called step(s) have completed their work.
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.
- Change the YourServer:YourPort values as needed by your installation. The URI might look something like https://MyPortal.MyCompany.com:443
- Remember that you will need to use HTTP or HTTPS, depending on your environment.
- The rest of the URI, /BWService/API/workflow/InvokeWorkFlow, will always be the same.
- Select POST from the “Method” drop-down list.
- Enter “application/json” in the “Content Type” field.
- Select the “Calling BW Task” checkbox.
- Enter the appropriate values in the “Body Information” section in the structure shown. This structure can be copied from here, pasted into your workflow, and the values changed as needed.
Finding the proper port needed will be in your IIS Manager, which can be found in Start → Windows Administrative Tools → Internet Information Services (IIS) Manager. There will be a drop-down for your server; then you will see Sites drop-down, and then Versago click on Versago, and on the right panel, there will be the proper port needed to use in the API call.
Here is a sample of the full URL. Copy and paste this string as a starting point.
https://MyPortal.MyCompany.com:443/BWService/api/workflow/InvokeWorkFlow
{
"pTaskID":"NN",
"pArguments":
{
"Arg1":"Value1",
"Arg2":"Value2"
}
}
- NN is the ID of the workflow being called.
- Arguments (parameters) are any values being passed to the workflow being called.
- Arguments are always sent in pairs. Each pair is separated by a colon : as shown.
- The argument (Arg1, Arg2, etc.) is the variable name expected by the workflow being called.
- Variable names are case-sensitive.
- Values are the value being passed.
- Text and dates are enclosed in double-quotes.
- Numeric values do not require double-quotes.
- “pArguments” is required even if no values are being passed. In this case, the “pArguments” section will look like this.
{
"pTaskID":"NN",
"pArguments":{}
}
