Stop Scratching Your Head
On a daily basis, a ServiceNow developer has the need to locate the source of functionality that is enabled via JavaScript.
This typically involves going to at least three or four different tables and running two or three searches per table, just to be sure. Often times, these searches end without any satisfactory result — especially when you’re trying to figure out how some complex native functionality works.
It’s impossible to know you’ve looked everywhere! In case you disagree, consider just how many places you might have to separately search:
- Business Rules
- Client Scripts
- UI Policies
- UI Actions
- UI Scripts
- Script Includes
- UI Pages
- UI Macros
- Script Actions
- Dictionary Field Reference Qualifiers
- Dictionary Field Calculations
- Activity Definitions
- Script fields on Activity Instances
- Intercepts
- Wizards
- Navigation Scripts
- Application Menu Modules
- Data Policies
- Assignment Rules
- Data Lookup Rules
- Inbound Actions
- Web Services
- Discovery Probes
- Discovery Sensors
- … and more… the list goes on and on.
In fact, there’s more than 245 script fields in a typical implementation, acrossed 165 different tables.
Start Searching!
Introducing Developer Search 3.2, the comprehensive utility to search every script field in the system for that troublesome piece of code.
This is the evolution of a similar tool that I’ve been using for 9 years now. I’ve improved the search algorithm to comprehensively capture every script field in the system that I’ve been able to find, and to do so in such a way that it will automatically find and search new script type fields that are added by plugins or custom development.
This tool also has an excellent feature “Search by Sys ID”. For those rare times that you find a hardcoded sys_id in some out of box ServiceNow script, and you have no idea what type of record it points to. Now you just plug in the sys_id, go get some coffee, and after a few minutes it’ll open the correct record.
Take a look for yourself at the screenshots below, and then give it a try! To the best of my knowledge, it should work properly on ServiceNow versions Aspen thru New York.
