hey everyone welcome back to another servicenow quebec quickies it is so good to have you here this video is brought to you by dot walk dot io dot walk dot io is the maker of bootstrap an ai powered way to populate servicenow atf with test cases based on the actual experiences in your servicenow system i love this tool because it relieves the most labor-intensive part of servicenow atf without requiring you to adopt some new framework check out the description below and see why dot lock.io is my most compelling use case for ai in the servicenow ecosystem and aldous international aldis is a staffing company serving the servicenow ecosystem by focusing on community collaboration and mentorship just check out their podcasts ai in action and ai mentors which in my opinion are great productions paying it forward within the servicenow ecosystem check out the links below and get in touch with director ben sparks and see why aldis is one of my few endorsed staffing agencies this episode is about a scorching red-hot new dev tool called script tracer script tracer is a super low friction way to watch all the server-side consequences of any given transaction let's see it in action first we're going to search the navigator bar for script tracer this will open up in a new window and we're going to say start tracer now we're going to create a new incident i'm just going to put a caller of larry fleming short description of test and i'm going to submit the incident let's go to check on the script tracer on its own it's logged out all the consequential business rules including business rules whose update triggered further business rules not only that but it's flagged areas where there were problems so we see with this question query there's an error that rp is not defined let's out check out the part of the script where that's a problem let's show the full script and it's important to note that wherever you are you can actually view the file that contains that script so i'm clicking view file and that's taking me to the business rule where that error was logged this is unprecedented developer troubleshooting power but the savvy amongst you might be asking how is this different from script debugger well script debugger requires you to establish log points and breakpoints script tracer is far more passive and just allows you to log the consequences of each transaction so in the duke's opinion script tracer is best for general discovery of transactional consequence whereas script debugger is for very specific logging of what specific scripts are running