Q: What causes Script Include Not Found in ServiceNow?

Script Include name doesn't match class name — Navigate to System Definition > Script Includes and open your Script Include record. The Name field must exactly match the class name defined in the Script field (case-sensitive). Even a single character difference will cause instantiation failures. Cross-scope access restriction — Check the Application field on both the Script Include record and your Business Rule. If they're in different scopes and the Script Include isn't marked as accessible from all application scopes, the instantiation will fail. Look at the Accessible from field on the Script Include. Script Include is inactive — Open the Script Include record from System Definition > Script Includes and verify the Active checkbox is checked. Inactive Script Includes cannot be instantiated even if the name and scope are correct. Syntax error in Script Include prevents loading — Check System Logs > System Log > All for JavaScript errors related to your Script Include name. Syntax errors in the Script Include code prevent the class from being registered, causing 'not a constructor' errors. Missing initialize function or incorrect class structure — Open the Script Include and verify it has a proper class structure with an initialize function if it's meant to be instantiated with 'new'. Check that the class is properly defined and not just a collection of static methods.

Question 1

What causes Script Include Not Found in ServiceNow?

Accepted Answer

Script Include name doesn't match class namehigh likelihood

Navigate to System Definition > Script Includes and open your Script Include record. The Name field must exactly match the class name defined in the Script field (case-sensitive). Even a single character difference will cause instantiation failures.

Cross-scope access restrictionhigh likelihood

Check the Application field on both the Script Include record and your Business Rule. If they're in different scopes and the Script Include isn't marked as accessible from all application scopes, the instantiation will fail. Look at the Accessible from field on the Script Include.

Script Include is inactivemedium likelihood

Open the Script Include record from System Definition > Script Includes and verify the Active checkbox is checked. Inactive Script Includes cannot be instantiated even if the name and scope are correct.

Syntax error in Script Include prevents loadingmedium likelihood

Check System Logs > System Log > All for JavaScript errors related to your Script Include name. Syntax errors in the Script Include code prevent the class from being registered, causing 'not a constructor' errors.

Missing initialize function or incorrect class structurelow likelihood

Open the Script Include and verify it has a proper class structure with an initialize function if it's meant to be instantiated with 'new'. Check that the class is properly defined and not just a collection of static methods.

Question 2

How do you fix Script Include Not Found in ServiceNow?

Accepted Answer

How to fix it Navigate to System Definition > Script Includes and search for your Script Include by name. Open the Script Include record and compare the Name field with the class name in the Script field. They must match exactly, including case. If names don't match, update either the Name field or the class name in your script to make them identical. Verify the Active checkbox is checked on the Script Include record. Check the Application field on the Script Include and note the scope. Navigate to your Business Rule at System Definition > Business Rules and check its Application field. If they're in different scopes, either set the Script Include's Accessible from field to All application scopes or use sn_app_scope.ClassName syntax in your Business Rule. Check for syntax errors by going to System Logs > System Log > All and filtering by your Script Include name. If you find JavaScript errors, fix the syntax issues in the Script Include and save the record. Verify your Script Include has an initialize function if you're instantiating it with the new keyword. Clear the instance cache by navigating to System Diagnostics > Cache Stats and clicking Flush All to ensure your changes are loaded. Test your Business Rule by triggering the condition that executes it.

Question 3

How do you prevent Script Include Not Found in ServiceNow?

Accepted Answer

Always use identical naming between the Script Include Name field and the class name in your script - ServiceNow is case-sensitive. Set Script Includes to 'All application scopes' in the Accessible from field if they'll be called from multiple applications. Use the Script Include template when creating new Script Includes to ensure proper class structure with initialize function. Test Script Includes in Scripts - Background before using them in Business Rules to catch syntax errors early. Document cross-scope dependencies and review them during application updates to prevent scope access issues.

Script Include Not Found in ServiceNow

Symptom

Possible Causes

Debugging this in a real instance?

Solution

How to fix it

Prevention Tips

Test Your Knowledge

Related Articles