Customise Background Scripts
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-19-2023 08:31 AM
Hello,
I want to limit script executions (via the Background Script Module - sys.scripts.do) that interact with major ServiceNow tables (dependant on User Group/Role) e.g.: prevent script execution on sys_user_group, sys_user_role, etc.
I also want to limit the scope selections dependant on User Group/Roles in e.g.: display Only Global Scope.
Something that comes to mind is via Active Transactions aborting the ones that do not meet my requirement but via Business Rules I haven't even been able to come up with a Proof of Concept to block Active Transactions
Is there any way I can manipulate the /sys.scripts.do page and/or Active Transactions Records to abort the script in an automated way?
Best Regards,
José Pires

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-20-2023 06:28 AM
Hi @JosePires,
I think you need to establish good governance around sys_scripts.do usage, or to make your developers use more Fix Scripts instead, which you can control code quality, when will run, and versions before going to production in a code review session.
As per your question, you can configure transaction quota rules, it allows you to define a quota policy for different types of transactions.
Existing quotas:
How to configure a new one:
If you found my answer helpful or correct in any way, please don't forget to mark it to help future readers! 👍
--
Kind regards,
Marcos Kassak
Solution Consultant 🎯