Copyright © Cloud Software Group, Inc. All Rights Reserved

Debugging Formflows

After validation, formflows can be tested in the Tester utility provided by TIBCO Designer.

At design time set the TIBCO BusinessWorks engine properties in the following file: bwfb_install_dir/version/bin/Properties.cfg.

To Debug a Formflow

•	Select Tools>Tester>Start to start the Tester utility, and start the formflow.

Figure 42 Select Process to Load

If a formflow depends on runtime data, this data must be manually provided when testing formflows in TIBCO Designer. Runtime data might include formflow context parameters, request parameters, or any process variables that must be specified at runtime.

For details on using the Tester utility, see the TIBCO BusinessWorks Process Design Guide.

Including Dynamically Called Forms and Formflows

Both form and formflow names can be specified at runtime. In a Call Formflow activity, the Process Name Dynamic Override field can be used, and in a Set Form Data activity, the form name can be mapped to the @FormPath parameter. However, when no explicit reference exists at design time, the form or formflow cannot be automatically called by the Tester utility.

To test a formflow that is called dynamically, load this formflow in the Tester utility at the same time as the parent formflow.

To Test a Formflow With Dynamically Specified Forms

1.	Create a mock formflow with a Show Form activity for each form specified at runtime. You must configure the Show Form activities to display the required forms, for example:

2.	Load this formflow in the Tester utility, at the same time as the parent formflow.

To View Error Information

If errors occur during testing, you can view detailed error information by doing the following:

•	Selecting Window>Show Console in TIBCO Designer

•	Viewing the formflow_debug.log file in the user_home_directory/.TIBCO/.formflow/Logs directory.

Copyright © Cloud Software Group, Inc. All Rights Reserved