Using Non-Reactive Debugging

You can develop scripts and debug them when connected to the Cisco Unified CCX server and once the script is working, you can upload it and create an application for using it.

Use the following procedure to debug scripts that do not require external events for their execution. This procedure is also useful for debugging script segments or subflows.

Tip

You can create a script that first uses the Place Call step to place an outbound call, and then continues the script using that outbound call. This procedure makes it easy to debug a script that is triggered by calls, without the complexity of uploading the script to the script Repository every time you want to debug and test it. All Media and Call Control steps need to use the call object that the Place Call step returns instead of the default “-- Triggering Contact --”.

Note

If you are using subflows, the debug process does not enter and debug the subflows. The debug process executes the subflow without providing debug controls while executing it. (This process is exactly like stepping over the Call Subflow step.)

Procedure

Step 1

With an existing or new script open in the Cisco Unified CCX Editor Design pane, choose Debug > Start from the Cisco Unified CCX Editor menu bar.

The Cisco Unified CCX Editor debugs the script and flags any errors.

Step 2

In the Cisco Unified CCX Editor, correct any errors flagged by system prompts.

Step 3

Continue to use the Debug command until you have cleared all error flags (messages).