This is an old revision of the document!
Table of Contents
Introduction (Bizweaver)
The Bizweaver application is set of tools used to automate data acquisition, data manipulation, file management activities, as-well-as providing data integration into SAP Business One. The various tools provided by Bizweaver are linked together as a set of sequential steps called a workflow.
Audience
This Wiki section is intended for developers of Bizweaver workflows. Knowledge of standard SQL (Microsoft T-SQL) statements is required.
Environment and Installation & Upgrade Information
End User Help
Bizweaver Application Overview
Building a Workflow
It is strongly recommended that prior to constructing a workflow you spend some time reviewing your requirements, workflow solution design options and approach, and what Bizweaver tools you may need. Workflow construction tends to be easier and more efficient because of this pre-planning.
Details for building a workflow are found here.
Execute a Workflow
There are three methods to execute a Bizweaver workflow: test/debug mode, “run now,” and scheduled. The results are the same for all methods.
Test/Debug Mode
The Bizweaver Test Run Tool allows a developer to execute a workflow in a step-by-step manner. Variable values can be examined at each step to confirm that they are what is expected. More information on this tool is found here.
Run Now
The “Run Now” option is used to execute a workflow while in Bizweaver. There are two ways to use this option.
First, the currently active workflow can be executed by clicking the “Run now” link as shown below.
Second, right-click on any workflow in the Workflow List area, and select the “Run now” option.
In both cases, the workflow is executed immediately. No feedback is provided while the workflow is executing (as seen in the Test Run tool).
Run Now Log
At the end of the execution a “Task Execution Status” window is automatically displayed showing the log information for the workflow.
In general, you will only need to scan the log records for information in the “Message” column. These will typically be error messages that may need attention.
Click on the Open Log File link to open a text file of log information. This file will have more technical information and can be saved for further review.
Click the [Close & Delete Log Records] button to delete the log information from the Bizweaver logging table, and close the window.
Click the [Close] button to close the window. An additional dialog will allow you to delete the log records here as well.
Note that the log records can be retained if desired. This can be helpful if you are doing reporting from the Bizweaver log table. See Appendix C – Activity Logging for more information.
Scheduled Execution
Bizweaver workflows can be automatically executed based on a schedule. This is the most common, and most efficient, way to execute workflows. See Workflow Schedules for more information.
Workflow Variables
“Variables” are data values that are held in memory during the execution of a workflow. There are two types of variables in Bizweaver: User Variables and Step Variables.
User Variables are defined by the user. These values can be defined in the Variables tool or they can be created using the VBScript tool.
Step Variables are special references created by the Bizweaver application. Most Bizweaver workflow tools create these variables as the step is executed. An example of this would be a reference to an output column from a SQL Command: Reader step.
Bizweaver variables are available to other workflow steps that follow the step where they are created.
More information is found on the Using Variables page.
Bizweaver Activity Logging
As noted earlier in this document, actions from the Test Run tool are logged in text files. However, when a schedule executes a workflow, or using the “Run now” option, step information is logged to the SQL database used by Bizweaver.
Transaction logging data is found in the table VGO_SYNC_PROC_LOG. An entry is made for each workflow step that is executed. In addition to workflow and step information, any errors reported from Bizweaver steps is recorded. This provides a mechanism for reporting execution issues.
The log table can be accessed via SQL Management Studio or from a report in Versago. Following is a SQL Select statement to access this information.
SELECT t0.JobID, t0.TaskID, t1.TaskName, t0.StepType, t0.Step, t0.[TIME], t0.Message FROM vgo_sync_proc_log t0 INNER JOIN VGO_SYNC_TASKS t1 ON t0.TaskID = t1.TaskID
The log information for a specific workflow can also be accessed using the “View Job Log” function described in the “Icon Bar” section of this document.
General Information
Tools
Additional Technical Information
