Script Include Scope and Accessibility Across Scopes

Quick Answer

This statement is correct because cross-scope access to a script include is not an all-or-nothing situation; ServiceNow gives you a dedicated 'Accessible from' property specifically to control which scopes are permitted to call a given script include, and that property can be set broadly to allow all application scopes or narrowed down to specific ones. This exists because script includes are isolated by scope by default, meaning a script include created inside one scoped application cannot normally be referenced or executed from a business rule, script, or other artifact living in a different scope unless something explicitly opens that door. Making a script include's scope Global is one well-known way to achieve broad cross-scope access, but the 'Accessible from' setting is the actual property governing that access, letting a developer be as permissive or as restrictive as the situation calls for rather than only choosing between fully isolated and fully global. Understanding this distinction matters because scope isolation exists to protect applications from unintended interference, so deliberately opening access should be a controlled decision rather than a default. When an exam question describes needing a script include to be usable from a different application scope, think in terms of which specific access-control setting governs that visibility, since ServiceNow typically offers a targeted property for this rather than requiring you to abandon scoping altogether.