Exception Handling
Warnings and errors are always output to the console but when an unrecoverable error has occurred a JavaScript error will be thrown. These errors bubble up to the top layer of the JavaScript API and are output as console error messages along with a stacktrace, if available.
When you are developing a view, you should test it and run with the developer tools open so that you can spot any console errors as early as possible. In some cases an error may only occur when certain data values are present. In these situations you may need to add in some data checking before processing.
Developer tools in most web browsers allow you to pause execution of JavaScript when an unhandled exception occurs. This is useful as you can then step through the code and also see what calls led up to the exception. As multiple browsers are supported in the Web Client, you need to test your custom views across the different browsers.
© 2001-2019 Fair Isaac Corporation. All rights reserved. This documentation is the property of Fair Isaac Corporation (“FICO”). Receipt or possession of this documentation does not convey rights to disclose, reproduce, make derivative works, use, or allow others to use it except solely for internal evaluation purposes to determine whether to purchase a license to the software described in this documentation, or as otherwise set forth in a written software license agreement between you and FICO (or a FICO affiliate). Use of this documentation and the software described in it must conform strictly to the foregoing permitted uses, and no other use is permitted.