To test a workflow, open the workflow design window. Click any of the test icons in the toolbar to initiate processing.

A new window is displayed at the bottom of the design canvas. A tester can view the workflow steps in this window as they execute and view variables as they become available. All execution options are in the workflow design canvas toolbar.

1. Automatically step through the workflow at speeds 1,2,3.
   1. Speed 1 executes a step every 2 seconds
   2. Speed 2 executes a step every second
   3. Speed 3 executes a step every .25 seconds
2. Execute a single step.
3. Pause automatic execution.
4. Stop testing
5. Display area showing the current step, steps that have been executed, any variable values viewed, and any error messages that may occur. This information is also displayed in the block at the bottom of the canvas.
6. Examine variable values (described below).
7. Undock from design canvas
8. Expand and refresh variable

Breakpoints are used when testing a workflow, and there is a need to stop at a specific step. Breakpoints can be set either in the workflow list view or by right-clicking a step and setting the breakpoint.

• Breakpoints only affect workflow testing
• They save when saving the workflow
• All breakpoints can be manipulated at once using the vertical ellipsis in the list view header.
  • Enable
  • Disable
  • Remove

One key feature of Testing a workflow is the ability to examine values during its execution. This is done in the ‘Examine Variables” area at the top of the test run window.

There are two drop-down list windows in this area. The drop-down on the left lists workflow steps that have been executed. These are the steps from which values can be viewed. The drop-down on the right shows the values (variables) that can be viewed for the selected workflow step.

When a variable is selected, its value is displayed in the field to the right. This is the value that will be available to subsequent steps.

Multiple values from multiple steps can be viewed at any time.

Using will either expand the variable to be viewed in its own window. Or refresh the variable.

Note that some variables are affected by the Bizweaver looping function. In these cases, the value displayed does not automatically change with each loop instance. The value must be refreshed by clicking the refresh button for the desired variable.

Testing executes each step of the workflow. If the workflow contains a loop, the tool will cycle through every record passed into the loop. For example, if the input list has 100 records, you will see the tool process the steps within the loop 100 times. In these cases, the “automatic” execution and execution speed tools are helpful. Or, as noted earlier, limit the number of input records during the testing process.

Test run information is written to a text file during the processing cycle. This file is available at the end of the run via the “Open in Notepad” button at the bottom of the workflow designer area below the design canvas.

“Open in Notepad:“ Access this option to open the log file.

“Running Log:“ This window can be collapsed using the icon to the right of its window.

These results are helpful when troubleshooting a workflow. Third Wave support may request that you send these logs if you report an issue. The log files can also be found in C:\Program Data\Bizweaver.

A test can be stopped at any time using the “stop” icon in the toolbar. Once clicked, the test window will close, and the log with the last test runs details will be the only thing displayed.

Home