versago:configuring_report_links
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
versago:configuring_report_links [2020/01/08 10:41] runger |
versago:configuring_report_links [2020/07/23 11:42] (current) |
||
|---|---|---|---|
| Line 28: | Line 28: | ||
| ====Link Conditions==== | ====Link Conditions==== | ||
| - | * **Conditions** can be used to control when an action link is active based on values in other columns. See //**[[#link_conditions|Link Conditions]]**// | + | * **Conditions** can be used to control when an action link is active based on values in other columns. See // |
| * Click the red <color # | * Click the red <color # | ||
| 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. | ||
| </ | </ | ||
| Line 67: | Line 67: | ||
| The **Crystal Report** action provides a way to execute a Crystal Report for presentation to the user. An example of how this could be used is where the main report is a list of customer invoices. A Crystal Report action could cause a copy of the invoice document to be generated using Crystal Reports. | The **Crystal Report** action provides a way to execute a Crystal Report for presentation to the user. An example of how this could be used is where the main report is a list of customer invoices. A Crystal Report action could cause a copy of the invoice document to be generated using Crystal Reports. | ||
| + | |||
| + | General information about configuring Crystal Reports for use with Versago and Bizweaver is found **// | ||
| {{ : | {{ : | ||
| Line 72: | Line 74: | ||
| Registration of the Crystal Report is the same as described for Crystal Reports in the // | Registration of the Crystal Report is the same as described for Crystal Reports in the // | ||
| - | <WRAP center round help 100%> | + | <WRAP center round help 80%> |
| Crystal Reports that use a specific value for execution (e.g. an invoice number) must have a parameter in their definition. The Link Parameters will show the parameter(s) as Destination Field(s) that are mapped to a Source Field from the main report. | Crystal Reports that use a specific value for execution (e.g. an invoice number) must have a parameter in their definition. The Link Parameters will show the parameter(s) as Destination Field(s) that are mapped to a Source Field from the main report. | ||
| </ | </ | ||
| + | |||
| ====Bizweaver Webservice Setup==== | ====Bizweaver Webservice Setup==== | ||
| Line 80: | 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%> |
| - | Prior to v2.3, calls to the Bizweaver API were only sent using GET. | + | Beginning with v2.3, calls can be made using <color # |
| </ | </ | ||
| - | |||
| - | 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=== | ||
| - | |||
| - | {{ : | ||
| - | |||
| - | * **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 " | ||
| - | |||
| - | <code html> | ||
| - | https://< | ||
| - | </ | ||
| - | |||
| - | * **< | ||
| - | * 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. | ||
| ===Calling Bizweaver Using POST=== | ===Calling Bizweaver Using POST=== | ||
| Line 127: | Line 109: | ||
| * Select the source value from the drop-down list in the Source Field. | * Select the source value from the drop-down list in the Source Field. | ||
| * Leave these two values blank if no parameters need to be sent to the workflow. | * Leave these two values blank if no parameters need to be sent to the workflow. | ||
| + | |||
| + | 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. | ||
| ====URL Setup==== | ====URL Setup==== | ||
versago/configuring_report_links.1578498111.txt.gz · Last modified: 2020/01/08 10:41 by runger
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial 4.0 International
