Fields available for filters

[Jamsta1912]

Hello,

Is it possible to reduce the number of fields available for including in filters on a list view, without removing read access to the fields themselves? For all task types, there are a lot of fields available to choose from and I'm finding that users get confused by this as they don't have an understanding of what each field does. I want to avoid having to add Read ACLs to the fields I want to hide - partly for the effort involved, and also because I'd like some of the fields to still be visible elsewhere.

So for example, let's say a user with visibility of incidents can see a variety of fields when looking at an incident in form view, but I would like to reduce his options for filtering to those fields I know he'll make us of: eg 'company', 'created', 'closed', 'location', 'short_description', 'priority'.

Regards

Jamie.

[LearnerSubho]

Dear Jamie,

Configure ACL for "add_to_list" operation on the required field.

User would not be able to add the columns which they won't have access.

For more info: Section 3 of Using Access Control Rules - ServiceNow Wiki

Thanks,

Subhankar

[Jamsta1912]

Hello Subhankar,

Thank you for your response. This doesn't achieve what I'm after unfortunately. Even with 'add_to_list' ACLs in place, users can still see the fields listed in 'choose field' in filters.

[Jamsta1912]

Hi all,

Anyone else have any thoughts on this?

Thanks

[JohnG3]

Hi Jamie,

Did you find a solution avoiding the Read ACL? I have a similar requirement.

Thanks,

John