Background script
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello @Sandeshyadav , Could you verify whether you have created any scoped application in the instance, as scope of the applications which were developed on that instance are available here.
Please refer:
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0863463
Regards,
Nishant
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @Sandeshyadav ,
Do you have any scope applications in your instance ? Please check attached screenshot as your references.
Follow thread : https://www.servicenow.com/community/developer-forum/background-script-shows-only-global-scope-on-te...
Please nark helpful & correct answer if it's worthy for you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello @Sandeshyadav ,
Global and Custom Scopes: This picker lets you choose the global scope or any custom application scope created directly on that specific instance (e.g., custom applications prefixed with x_).
I have custom Demo app so I can choose my application in BG script as Below:
The native dropdown selector deliberately omits certain application scopes to maintain security and baseline integrity
If you found my solution helpful please accept the solution and mark it as Helpful.
Regards,
Prajakta
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @prajaktakha,
Please refer to the ServiceNow articles below for details on why an installed scoped application from a repository does not appear in the Background Scripts scope selector:
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0751600
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0863463
The available options are to either create and run a Fix Script or create a Cross-Scope Privilege record.
I hope this helps! If this resolves your issue, please consider marking this reply as Helpful or Accept as Solution.
Regards,
Harish