- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-28-2017 08:02 AM
Is there any way to restrict the ability to 'Export Directly from URL' without affecting read access for a user?
Export Directly from URL:
https://docs.servicenow.com/bundle/istanbul-servicenow-platform/page/administer/exporting-data/task/...
I'd like to specifically control export without affecting read.
Solved! Go to Solution.
- Labels:
-
Instance Configuration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-28-2017 09:25 AM
You can block URL access to exporting by Excel by creating an ACL on the ExcelOutputProcessor like so:
N.B. This will not stop a user from exporting via the Context Menu drop down UI on the list.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-28-2017 09:25 AM
You can block URL access to exporting by Excel by creating an ACL on the ExcelOutputProcessor like so:
N.B. This will not stop a user from exporting via the Context Menu drop down UI on the list.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-28-2017 10:16 AM
Thank you Matthew. It appears that 'Processor ACL rules' only restrict by role. You can't set a condition or use the 'Advanced' option to write your own script. I'm afraid I don't want to restrict access by role. Any other thoughts?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-28-2017 10:34 AM
I'm not sure why it appears that way to you. There are out-of-box processor rules that use the script field and conditions field and it works fine for me when I am using admin. Do you need to elevate privileges? Not sure...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-28-2017 10:46 AM
FYI - I am on Istanbul Patch 3.
I'm pretty sure that a client script called 'Disable script for out of scope tables' is the culprit