error in client callable script include ACL
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-28-2025 05:08 AM
i am creating ACLS's for client callable script includes on a custom application.
here i got 2 script includes having with same name . one is on custom app and another is on Global application.
i am creating acl for custom scope script include, i am getting error by saying-- "Invalid Access control record as it cannot protect an outside page, processor, or script. The script include named "** script include name **' is in application 'Global', but the current application is "** custom app**.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-28-2025 05:19 AM
You will probably run into more issues with having the same name, even though it is in a scoped application. I think it would be better to rename the scoped SI.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-28-2025 05:23 AM
I agree with Mark here.
Change the name and see if any error and share us the updates
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-28-2025 06:19 AM
@VSN As a thumbrule one should not mix names of scoped script include with the global ones. Keep the names distinguished and you won't face such errors.