#Servicenow script debugger not working how to
#Servicenow script debugger not working update

The Scripts - Background Utility appears. Go to System Definition > Scripts - Background.

#Servicenow script debugger not working how to

Viewing and Killing Active Transactions How to find the Scripts - Background UtilityĢ. You can kill the job fortunately, just don't rely on this feature too much. You started a background script, and realized it is not working correctly. Sometimes we get a little too confident with our work and are similar to Icarus. He ignored instructions not to fly too close to the sun, and the melting wax caused him to fall into the sea where he drowned.

The main story told about Icarus is his attempt to escape from Crete by means of wings that his father constructed from feathers and wax. In Greek mythology, Icarus is the son of the master craftsman Daedalus. This is really needed in cases when you are updating tasks and the last updated time affects an sla or the tasks that have a lot of business rules on them you want to ignore. In the example above the setWorkflow and autoSysFields statements avoid those workflow and autoSysFields from being run or updated.

#Servicenow script debugger not working update

toSysFields(false) //Do not update system fields tWorkflow(false) //Do not run business rules Here is an example on how to avoid this: updateCI() When you are mass updating records with a background script, sometimes you don't want to run the business rules/workflow on every record you updated or have your name and the last updated time be when you updated it. Use setWorkflow(false) and autoSysFields(false) However either one you pick, they are both helpful to troubleshoot issues with your script or with just general troubleshooting 4. gs.log is kind of nice if you have a log-running query. However you can also use gs.log to print the results to the Script Log. In #2 above, I used a gs.print statement to print the rowcount of the query. When you ready to run that script and it is going to update the right number of rows, uncomment out the update line and run again. *** Script: grCI Query: name=SAP WEB03 = 1 With this example, it will return how many rows are going to be updated before you update. Gs.print('grCI Query: ' + grCI.getEncodedQuery() + ' = ' + grCI.getRowCount()) Comment out your update statement and add a RowCount statement until you are sure it is ok. If you are doing an update statement in your background script. RowCount and Comment Out Update Statement If I was doing a delete or update statement in the background script, this would not be good. This is an honest mistake, but since that column doesn't exist ServiceNow will ignore the query and return all records. In the bad script the column name in the cmdb_ci is not sys_name, it is name. Here is an example:īad Script: Accidentally Finds all CIs findCI() If you are doing a glide record query and your query is not designed correctly, ServiceNow javascript will ignore the query and not produce an error. Here are a couple points to help you avoid unknown disasters with Background Scripts 1. Remember how I said about how powerful background scripts are? I really mean this, I have seen data destroyed, access revoked, and system shutdown from background scripts. Please read how to be careful with Background Scripts first, before you get into it: Tips and Tricks You need to be extra careful in running background scripts.Īlways test Background Scripts first in a development instance. With great power comes great responsibility.īackground Scripts are so powerful that you can cause major issues to your ServiceNow system with the right script. Sometimes a background script can be created in minutes that solves the issue. It might not be feasible to use the list editor to update 200K records or make a csv file to update the records. However, that is not the most efficient way to update data in cases. Importing Data to create, update, or delete records Manually creating, updating, or deleting records In ServiceNow, you can get around using background scripts by using these other methods Background scripts are very powerful and can do complex operations in a short amount of time. It is also greatly helpful in troubleshooting records and running complex scripts to find information. What is a Background Script? It is an utility in ServiceNow to run scripts in the background, which is useful for mass create, update, and delete of data.