- 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-20-2014 11:47 PM
Hi Reach aparna,
You can make the field as protected.
Please refer the below link for further details
http://wiki.servicenow.com/index.php?title=Requiring_Fields_on_a_Form
Thanks,
Pradeep Sharma
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-21-2014 12:17 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-21-2014 12:22 AM
Also You will have your custom fields .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-21-2014 02:28 AM
If those fields are not used for any purpose in your instance, you can either deactivate them in the Dictionary or use an ACL to make them readable only by admins (or another role your users do not have).
Blog: https://sys.properties | Telegram: https://t.me/sys_properties | LinkedIn: https://www.linkedin.com/in/slava-savitsky/