When creating a class and its prototype, must the Script Include name match the class name?

When creating a class and its prototype, must the Script Include name match the class name?

• A. True
• B. False
• C. Depends on the class
• D. Always false

Answer: (A)

In ServiceNow Script Includes, the name of the Script Include becomes the constructor you use to create instances. The class you define inside is tied to that Script Include’s name, so you instantiate with new ScriptIncludeName(). For example, if the Script Include is named InventoryHelper, you typically define the class as InventoryHelper = Class.create(); InventoryHelper.prototype = { initialize: function(){}, ... }; Then you create an instance with new InventoryHelper(). If you tried to instantiate with a different name, there wouldn’t be a corresponding constructor exposed, leading to errors. This is why the Script Include name must match the class name used to instantiate.

In ServiceNow Script Includes, the name of the Script Include becomes the constructor you use to create instances. The class you define inside is tied to that Script Include’s name, so you instantiate with new ScriptIncludeName(). For example, if the Script Include is named InventoryHelper, you typically define the class as InventoryHelper = Class.create(); InventoryHelper.prototype = { initialize: function(){}, ... }; Then you create an instance with new InventoryHelper(). If you tried to instantiate with a different name, there wouldn’t be a corresponding constructor exposed, leading to errors. This is why the Script Include name must match the class name used to instantiate.