This is an old revision of the document!
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.
This Wiki section is intended for developers of Bizweaver workflows. Knowledge of standard SQL (Microsoft T-SQL) statements is required.
An overview of the Bizweaver application can be found here.
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.
Details for executing a workflow are found here.
“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.
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.