versago:configuring_report_links

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
versago:configuring_report_links [2020/05/15 15:14]
runger [Crystal Report Setup]
versago:configuring_report_links [2020/07/23 11:42] (current)
Line 59: Line 59:
 In this example, the customer code (BP Code) and customer name (BP Name) are being passed into the form. In this example, the customer code (BP Code) and customer name (BP Name) are being passed into the form.
  
-<WRAP center round help 100%>+<WRAP center round help 80%>
 If the value passed to the form is the primary key (e.g. vgoRecNum or whatever it has been named) the application will automatically execute a lookup for the record of the value passed. If the record is found the remaining fields will be populated. If the value passed to the form is the primary key (e.g. vgoRecNum or whatever it has been named) the application will automatically execute a lookup for the record of the value passed. If the record is found the remaining fields will be populated.
 </WRAP> </WRAP>
Line 83: Line 83:
 A **Bizweaver Webservice** link allows a user to execute a Bizweaver workflow from a report using the Bizweaver API. These workflows can be used for a variety of background processing. A **Bizweaver Webservice** link allows a user to execute a Bizweaver workflow from a report using the Bizweaver API. These workflows can be used for a variety of background processing.
  
-<WRAP center round tip 100%> +<WRAP center round tip 80%> 
-Beginning with v2.3, calls can be made using GET or <color #ed1c24>POST</color> POST provides authentication that is not available using GET.  Using the **POST** option is strongly recommended.+Beginning with v2.3, calls can be made using <color #ed1c24>POST</color>. Using the **POST** option is required in newer versions of Bizweaver.  Any links that use GET must be updated as soon as possible.
 </WRAP> </WRAP>
  
Line 111: Line 111:
  
 The “Destination” value is the string that calls the Bizweaver web service and passes any parameters that are needed. When parameters are specified in this string the are automatically set as Destination Fields in the Parameters section. Each parameter then needs to be matched to a Source Field from the report using the drop-down lists. The “Destination” value is the string that calls the Bizweaver web service and passes any parameters that are needed. When parameters are specified in this string the are automatically set as Destination Fields in the Parameters section. Each parameter then needs to be matched to a Source Field from the report using the drop-down lists.
- 
-===Calling Bizweaver Using GET=== 
- 
-{{  :versago:reports18.png?800  |}} 
- 
-  * **Method** is GET. 
-  * **Task ID** is not used for GET. 
-  * **Destination** is the URL needed to contact the Bizweaver web service. 
-      * All values to be used to execute the Bizweaver workflow are included in the "Destination" string when using the GET option. 
- 
-<code html> 
-https://<YourURL>/BWService/api/workflow/InvokeWorkFlow?pTaskID=NN&pStartAfter=0&pArguments={Parameter:Value} 
-</code> 
- 
-  * **<YourURL>** is the URL to your Bizweaver web server.  It should include the actual URL and port number. 
-    * Use HTTP or HTTPS as needed by your site 
-    * If Versago uses HTTPS the Bizweaver web service must use HTTPS as well. 
-  * **Task ID** is the target workflow ID defined in Bizweaver. 
-  * **Arguments** are any values that need to be passed to the workflow. 
  
 ====URL Setup==== ====URL Setup====
versago/configuring_report_links.1589570055.txt.gz · Last modified: 2020/05/15 15:14 by runger