Security Data Filters not working for HR Case tables

Jesse Jones
Tera Expert

Hello HRSD community.

My organization currently uses Data Filtration to secure some HR Case and HR Tasks records. I have learned that Data Filtration is being deprecated and being replaced with the new "Security Data Filter" functionality:

 

https://www.servicenow.com/docs/bundle/zurich-platform-security/page/administer/security/concept/sec...

 

https://www.servicenow.com/community/upgrades-and-patching-forum/security-data-filters-in-servicenow...

 

I have built a new security rule using a Security Data Filter but it is not functioning at all.

 

Here is the Security Data Filter record:

 

2025-09-05_12-03-14 - Security Data Filter.png

You can see that I have applied a filter condition so that the scope of the Data Filter includes cases created after a certain date and are assigned to a particular assignment group. It successfully found 1 record matching that condition, which I know is the correct record.

Here is the Security Attribute:

2025-09-05_12-06-08 - Security Attribute.png

You can see that I set the Type to "compound", then used the Group attribute to specify either the assignment group I listed in the Data Filter or our HR Core Admin group.

The "HR for HR" group I included in each record has only 1 group member, so if I log in as an HR Agent other than that member, I should not see the record assigned to the group. But I am seeing it as invalid agents:

2025-09-05_12-09-44 - Invalid user able to see HR Case.png

As far as I can tell, the Security Data Filter is totally inoperable. What am I missing?

Thank you!

2 REPLIES 2

M Iftikhar
Mega Sage

Hi @Jesse Jones

 

Have you checked other security rules?

Please verify that there are no other security rules, such as ACLs, that might be overriding the "Security Data Filter." Disabling or modifying conflicting ACLs for the HR Case table [sn_hr_core_case] may be necessary to allow the "Security Data Filter" to take precedence.

 

This could be the reason otherwise it is a "Security Data Filter" bug no doubt.

 

Thanks & Regards,
Muhammad Iftikhar
If my response helped, please mark it as the accepted solution so others can benefit as well.

pradnyajamgaonk
Tera Contributor

Hi @Jesse Jones  

 

Is this working for you, did you get any solution or any update from ServiceNow? I am having similar requirement and after implementing new security data filter it is not working same as old data filtration rule.