Script Include Usage Tracker

[shivamvish160]

PR Description:

Script Include Usage Tracker

A utility Script Include to help ServiceNow developers identify where a specific Script Include is being referenced across the instance. This is especially useful during refactoring, cleanup, or impact analysis.

Features

• Scans multiple tables for references to a given Script Include.
• Outputs a list of locations including table name, record name, and sys_id.
• Easily extendable to include more tables or fields.

Installation

1. Navigate to System Definition > Script Includes in your ServiceNow instance.
2. Click New and paste the code from ScriptIncludeUsageTracker.js.
3. Save and make sure the Script Include is Client Callable = false.

Usage

You can run the Script Include from a background script or another Script Include like this:
var tracker = new ScriptIncludeUsageTracker();
tracker.findUsage('MyScriptInclude');

Pull Request Checklist

Overview

• Put an x inside of the square brackets to check each item.
• I have read and understood the CONTRIBUTING.md guidelines
• My pull request has a descriptive title that accurately reflects the changes and the description has been filled in above.
• I've included only files relevant to the changes described in the PR title and description
• I've created a new branch in my forked repository for this contribution

Code Quality

• My code is relevant to ServiceNow developers
• My code snippets expand meaningfully on official ServiceNow documentation (if applicable)
• I've disclosed use of ES2021 features (if applicable)
• I've tested my code snippets in a ServiceNow environment (where possible)

Repository Structure Compliance

• I've placed my code snippet(s) in one of the required top-level categories:
  • Core ServiceNow APIs/
  • Server-Side Components/
  • Client-Side Components/
  • Modern Development/
  • Integration/
  • Specialized Areas/
• I've used appropriate sub-categories within the top-level categories
• Each code snippet has its own folder with a descriptive name

Documentation

• I've included a README.md file for each code snippet
• The README.md includes:
  • Description of the code snippet functionality
  • Usage instructions or examples
  • Any prerequisites or dependencies
  • (Optional) Screenshots or diagrams if helpful

Restrictions

• My PR does not include XML exports of ServiceNow records
• My PR does not contain sensitive information (passwords, API keys, tokens)
• My PR does not include changes that fall outside the described scope

[bird-03]

@shivamvish160

Good Contribution!
Seen very often we try to investigate the script reference using instance scans and this utility SI good to have for all developers

Keep Contributing and Happy Hacking !!