1. To begin, open the Control Properties for the button.
2. Click on the [Action] button to open the Action Properties page.
3. To create a new button action:
   1. Enter an Action Name. This is used for reference only.
   2. Action Type is Service.
   3. Action Sequence
      1. 1 if the invocation is from a custom button.
      2. 2 if the invocation is (Save & Close or Save & New) from a standard button.
   4. Service Type is POST.
   5. Action Target as described below.
   6. Action Trigger
      1. Primary Action if the invocation is from a custom button.
      2. Action Success if the invocation is from a standard (Save & Close or Save & New) button.
   7. Validate True Value is SUCCESS.
   8. Validate Error Message is 0.
   9. Validate Success Message is 1.
4. To modify a button action:
   1. Click on the desired Action Name.
   2. The existing information is displayed
   3. Make whatever changes are desired
5. Click the [Add/Update] button to save the action changes.
6. Click the [Save] button to save the button changes.

The Action String to invoke a Bizweaver workflow using POST* is shown below. http://1:2/BWService/api/workflow/InvokeWorkFlow The elements in red are specific to your installation. The other items (included variable names used by Bizweaver) are case sensitive, so the easiest way to create the Action Target is to copy this string and paste it into Versago, then make the needed changes. You might also update the Bizweaver server information so that you will only need to change a few items. - The server where Bizweaver is installed - The port assigned to the Bizweaver web service when the application was installed. ===== Bizweaver Action Target String Samples ===== - Example using HTTP to port 8082 on server “TWBSTestserver.demo.com”, invoking workflow ID 10, and sending a value from form control name “vgoRecNum” to a Bizweaver variable named “vgoRecNum.”

http://TWBSTestserver.demo.com:8082/BWService/api/workflow/InvokeWorkFlow?pTaskID=10&pStartAfter=0&pArguments={vgoRecNum:'~5~'}

- Example using HTTPS to port 443 on server “TWBSTestserver.demo.com”, invoking workflow ID 10, and sending a value from form control name “vgoRecNum” to a Bizweaver variable named “vgoRecNum.” Note that the only difference is the “HTTPS” and port number.

https://TWBSTestserver.demo.com:443/BWService/api/workflow/InvokeWorkFlow?pTaskID=10&pStartAfter=0&pArguments={vgoRecNum:'~5~'}

- Example using HTTP to port 8082 on server “TWBSTestserver.demo.com,” invoking workflow ID 10, and sending two values; one from form control name “vgoRecNum” to a Bizweaver variable named “vgoRecNum” and a static value “TextString” to a Bizweaver variable name “vgoText.”

http://TWBSTestserver.demo.com:8082/BWService/api/workflow/InvokeWorkFlow?pTaskID=10&pStartAfter=0&pArguments={vgoRecNum:'~5~',vgoText: 'TextString'} ===== Versago and Bizweaver Complete Example ===== Information captured on Versago Form Configuration in Versago form button This configuration can be applied on the [Save & New] and [Save & Close] buttons. It should not be applied on the [Save] button since you probably don’t want Bizweaver processing to occur until the user is finished with the input record. Also note that if you have both the [Save & New] and [Save & Close] buttons active, the configuration needs to be applied on both buttons. Configuration in Bizweaver**

The values from Versago are captured in a Variables step at the beginning of the Bizweaver workflow.