Debugging applications Application developers can display debug messages about configuration records to help them troubleshoot issues. The system offers the following debugging options to help application developers determine how applications affect configuration records. Table 1. Application debug options Debugging option Description Debug Business Rule Use this module to determine which application's business rules are running against tables. The system only displays application information if business rules from different application scopes run on the same table. Debug Business Rule (Details) Use this module to determine the results of running business rules against tables. The system only displays application information if business rules from different application scopes run on the same table. Debug Security Use this module to determine which application's access controls apply to a given table or record. Debug Scopes Use this module to determine the application scope context in which a script runs. Since one script can call another script it is possible to have multiple application scope context changes while running a series of scripts. Enable Session Debug Use this related link to enable the generation of log messages for a particular application. Application scripts that use GlideSystem logging methods will generate output to the log at the indicated verbosity level. When multiple applications contribute to the debug output, the system adds a new section called Apps to the display a list of the applications writing to the session log. Clicking on the check box next to the application name hides or displays the application's associated debug messages. Figure 1. Sample application debug output of business rules Debugging scopesApplication developers can use the Debug Scopes module to display information about when the system switches between custom applications to run server-side scripts.