- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-20-2014 11:09 PM
Hi,
I have a custom table that extends Task table and have created two new fields 'Category' and 'Subcategory' as reference fields in my custom table.
While personalizing the form/list, I don't want the Task table fields with the same name (Category and subcategory) to be available in the left slush bucket for the selection since these fields are not being used. Is there a way to hide/remove these fields from the slush bucket so that user can't select these unused fields at all ?
Thanks,
Reach
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-21-2014 12:53 PM
You could still use ACLs for this, i.e. have an ACL for the field on Task table to deny access (at Task table level) and have separate ACLs for the same field for tables that extend Task (e.g. Incident, Change, etc.) to allow access on that level. ACLs on child table override ALCs on the base table. More information is available here:
Using Access Control Rules - ServiceNow Wiki
Blog: https://sys.properties | Telegram: https://t.me/sys_properties | LinkedIn: https://www.linkedin.com/in/slava-savitsky/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-21-2014 09:46 AM
Hi Pradeep/Vimal/Slava,
Thanks for you replies.
My requirement is like this :
The task table fields 'Category' and 'Subcategory' should not be available in the left slush bucket for the selection on 'right click -> personlize' in my application.These fields should not be visible in the slush bucket.
Since, Task table and these fields are being used by many other tables on my instance so I cannot directly modify these fields or run any ACLs on this field.
Is there a way to make a field inactive by Dictionary override ?
Thanks,
Reach
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-21-2014 12:53 PM
You could still use ACLs for this, i.e. have an ACL for the field on Task table to deny access (at Task table level) and have separate ACLs for the same field for tables that extend Task (e.g. Incident, Change, etc.) to allow access on that level. ACLs on child table override ALCs on the base table. More information is available here:
Using Access Control Rules - ServiceNow Wiki
Blog: https://sys.properties | Telegram: https://t.me/sys_properties | LinkedIn: https://www.linkedin.com/in/slava-savitsky/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-21-2014 02:06 PM
Hi Slava,
Thanks a lot and you are 100% correct that I can achieve this by ACLs..Working for me
Thanks a lot !
Reach
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-18-2017 04:42 AM
Hi Aparna,
Can you tell how you resolved it? What ACL you wrote? I have the same requirement .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-21-2017 12:06 PM
Hi Anubhav,
Can you try creating 'add_to_list" ACL with role "admin" only? OR if you want to restrict it to all, you can set answer = false in the script.
Thanks,
Aparna Sharma
Aparna Sharma | HRIS | ServiceNow | Work at Lightspeed
(o) 669-262-1635