---
sourceDocument: Xanadu API Reference
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/api-reference

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu API Reference

ft:clusterId :

    - crapiref

bundleId :

    - crapiref

workflow :

    - Creator


---

# Writing to the debug log

# Writing to the debug log {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

To write to the debug log in your client-side JavaScript, or UI policies, make a call
to the global function `jslog()`.  
An example of using `jslog()` in JavaScript:

    function logData (r ) {
        lastLogDate  = r. responseXML. documentElement. getAttribute ( "last_log_entry" ) ; var items  = r. responseXML. getElementsByTagName ( "log" ) ;
        jslog ( "response=" + r. responseText ) ; }

Additionally, when client scripts run, the name of
the client script and timing information is displayed. This can be useful in determining which
scripts are running and whether they are impacting
performance.

## Debug UI policies {#ariaid-title2}

Enabling the glide.ui.ui_policy_debug property lets you monitor the
processing of UI actions.  
Here are some sample log events from an incident policy that sets fields to read-only if the incident_state is closed.

    GlideFieldPolicy: Evaluating condition
    GlideFieldPolicy:     incident_state (7) = 7 -> true
    GlideFieldPolicy: --->>> TRUE
    GlideFieldPolicy:    Setting opened_at disabled to true
    GlideFieldPolicy:    Setting opened_by disabled to true
    GlideFieldPolicy:    Setting closed_at disabled to true
    GlideFieldPolicy:    Setting closed_by disabled to true
    GlideFieldPolicy:    Setting company disabled to true

## Access the JavaScript log {#ariaid-title3}

JavaScript that runs on the browser, such as client scripts, can include a call to
jslog() to send information to the JavaScript Log. Users with the admin role can access this
log.

### Before you begin

Role required: admin

### About this task

The steps to access the JavaScript debug window depend on which UI version you are using.  
Note:  
The JavaScript debug window is not supported with Next Experience in Utah. For more information about supported features in Next Experience, see [Considerations for activating Next Experience](https://www.servicenow.com/docs/access?context=next-experience-adoption-paths&version=xanadu&pubname=xanadu-platform-user-interface&ft:locale=en-US).

### Procedure

1. Open the JavaScript log by navigating to the appropriate location for your version of the UI.  

   |-|-|
   | Core UI | 1. Click the gear icon in the banner frame. 2. Click the Developer section. 3. Toggle the JavaScript Log and Field Watcher switch. {#t_JavaScriptLog__ol_rf2_2dq_ms} |
   | UI15 | 1. Click the gear icon in the banner frame. 2. Click JavaScript Log and Field Watcher. {#t_JavaScriptLog__ol_em3_kdq_ms} |
   | UI11 | Click the debug icon (![The debug icon]()) in the banner frame. |
   [ ]

   {#t_JavaScriptLog__simpletable_HowToOpenJavaScriptLogAndFieldWatcherInDifferentUIs}  
   A new pane opens at the bottom of the screen. It shows the JavaScript Log tab and may also show the Field Watcher tab.
2. If needed, select the JavaScript Log tab.
3. Click the clear icon (![The clear icon]()) to clear the contents of the log, as needed.