Using the On Exception Goto Step

The On Exception Goto step of the General palette of the Cisco Unified CCX Editor sends the execution to a specified place in the script when an exception is generated, which allows you to provide logic in the script for handling exceptions.

Note

You must check the engine log file, present in [Cisco Unified CCX Install Directory]/log/MIVR directory, corresponding to the time of exception to recognize the specific exception that has occurred. For example: com.cisco.wf.subsystem.obj.WFInvalidStateException.

By using the On Exception Goto step for a specific exception in a script, you can register a new handler for a given exception or override a previously existing one.

The registration process is for the complete script, so it does not matter where the exception occurs (before, during, or after the given step). Once the step executes, the handler is registered until either a new one is re-registered or the exception is cleared with the On Exception Clear step of the General palette.

If an exception results in a subflow, the script first consults the exception handlers of the subflows. If none are defined for the given exception, the exception aborts the subflow and the Cisco Unified CCX Engine looks for exception handlers in the parent script and so on until either an exception handler is found or the script aborts completely.

If no exception handlers are registered, the script aborts and error handling falls back to the last level of error handling, which is the default script.