task table access issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2022 10:10 AM
In a case table we have Parent field
From the service portal contact want to access the field.
but when he clicks on parent from case table in the portal it is showing "No matches found"
Can you please help me for the same how to resolve the issue.
- Labels:
-
Customer Service Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2022 10:29 AM
Hi
User doesn't have access to task table hence you are seeing this, Give read access to user and it will solve your issue, but honestly it's not best practice to give even read access to users so if possible just hide the field.
Regards
Regards,
Musab
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2022 10:54 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
Hi @Chandrima Mukh2 ,
If we provide read access to the user they will be able to see all the child records which has task as parent. This may cause security issues.
Please mark my answer correct and helpful if this works for you.
Thanks and Regards,
Suneesh
Thanks and Regards,
Suneesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-28-2025 02:24 PM
Here's a recent update on this issue from ServiceNow,
Problem No: PRB1915184
Problem Subject: Security constraints prevent access to the requested page when visiting task.list
Problem Description: Failing a Deny ACL from anywhere in the hierarchy will prevent table access to the list of a parent table
Problem State: Fixed
Problem Fixed In: Yokohama Patch 8, Yokohama Patch 9, Zurich Patch 2, and Australia releases
Need to know what changed on this instance overnight???
Failing a Deny ACL from anywhere in the hierarchy will prevent table access to the list of a parent table,
This is a regression issue on our side that started occurring from Yokohama Patch 7 and later versions.
The temporary workaround will resolve the issue until you upgrade to a fixed version.
Please note that Yokohama Patch 8 and Zurich Patch 2 are now available for upgrade.
Solution Proposed:
The workaround is to create the property
'glide.security.enable_detailed_table_level_acl_check'
.Set property
"glide.security.enable_detailed_table_level_acl_check"
to false to skip the detailed hierarchy checks for the initial table access decision. This will check the direct table for roles and security attributes to determine initial table access. READ operations on the records/fields will remain unaffected, for now. And, our dev team internally created a problem (i.e., PRB1915184) for a permanent fix.
Please clear the cache after performing the workaround.
Note: Once you upgrade to the fixed version, the System Property
glide.security.enable_detailed_table_level_acl_check"
must be re-enabled.
