Testing and Debugging ActiveVOS Central Forms

ActiveVOS Designer User’s Guide

Testing and Debugging ActiveVOS Central Forms

After you deploy one or more process request forms and task forms, you can test and debug your Javascript by using a browser Javascript Debugger and enabling debugging in ActiveVOS Central. You can also use the JSON Converter utility.

To debug your Javascript in HTML forms, do the following:

Install or enable a Javascript debugging tool in your browser, such as Firebug for Firefox, built-in debugging in Internet Explorer or the Developer JavaScript Debugger in Chrome.
To enable debugging in ActiveVOS Central, add the following command to the ActiveVOS Central URL as follows:

http://localhost:8080/activevos-central/avc/avc.jsp?debug=true

Use the ActiveVOS JSON Converter tool to check the conversion of JSON to XML and vice versa. Check what a JSON request form looks like in XML or generate sample XML data and convert to JSON.

Access the converter at:

http://localhost:8080/active-bpel/jsonConverter.html

When you make changes in your form and redeploy it, you can select Reset Form in ActiveVOS Central to view the updated form.

With debug enabled, it is easier to debug jQuery functions. They get expanded into readable lines of code instead of the one long line of code that typically shows in a debug console.

For task forms, you can also use Development Mode for testing layouts without redeploying the form.

Tips for testing forms:

Be sure that your HTML forms are well-formed XML. ActiveVOS validates forms and provides warnings if there are invalid tags.
Be sure to use lower-case element names that are schema-valid
Check that all tags are properly closed with end tags
In HTML markup, mixed types are not supported. For example, within an XML message element, you cannot add HTML tags, such as <contactName><b>Georgia Jane</b></contactName>
HTML element ID attributes must end with $ID suffix, such as processRequestForm$ID. The $ID suffix provides a unique HTML element ID to avoid collisions with other forms.
JavaScript reserved words, such as in and out are not allowed as JSON data parts. If your schema contains an element named as a JavaScript reserved word, you may see a blank form in some browsers. To correct the problem, you must change the JavaScript portion of your form as shown in the example:

Incorrect: getText(parametersTaskInputPart.NewOperation.in) where in is an input message for NewOperation.

Correction: getText(parametersTaskInputPart.NewOperation["in"])