Preview an App in Debug Mode

When testing your application, you typically preview it to see it the way your user would. Sometimes though, you might want to preview the application in debug mode to troubleshoot issues with the Visual Builder runtime and Oracle JET libraries—runtime dependencies that make sure your app works as intended.

The Preview option in the header facilitates both modes:

Description of the illustration preview.png

The default Preview mode uses the optimized variants of the VB runtime and JET libraries. In this mode, all unnecessary characters (such as whitespaces and comments) in the application's source code are removed and variable names shortened to minify code and optimize performance.

The Debug Preview mode, on the other hand, uses the debug variants of the VB runtime and JET libraries. In this mode, line breaks and white spaces are preserved, allowing you to view the application's source code in a more readable format. You can then use your browser's debugging tools to step through your code and figure out exactly where an error occurred.

Because no performance optimization is done in debug mode, previewing an app in this mode can be misleading about how quickly—or slowly—an app opens. As a result, you might want to use debug mode only in a development environment.

• To view your app like a user would with the pages and data displayed, click .
• To view your app in debug mode, click the Preview drop-down, then select Debug Preview .