Helpful Hints to Debug your Application
When trying these examples, and more importantly, when testing and debugging commands in your own applications, try the following:
-
Make an audit trail in the CMCalls .TXT file. To do so, set ‘Write text to data file’ to ‘checked’ in all of your modules; this will write the module number, the label field, and any touch-tones to the CMCalls .TXT file.
-
When using a variable, it is a good idea to print it to CMCalls .TXT by using the Print command in your scripts.
-
As you test, listen carefully to any prompts or modules you hear, and check the CMCalls .TXT file to follow the progress of the call.
Once your application is correct, consider setting the ‘Write text to data file’ back to ‘unchecked’ to help cut down the size of the CMCalls .TXT file.
The CMCalls .TXT file is great for debugging in that you can see a step-by-step log of the application. If something went wrong, you can follow along in the CMCalls .TXT file to see where the error occurred so that you can debug the application.