DevOps Change Workspace Home page error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
As a DevOps user, I am encountering the below error while logging in as a devOps user or devOps admin. I have already created the query_range ACL and assigned both the sn_devops_ws.workspace_user and sn_devops_insights.user roles. Since the Home page includes DevOps Insights, this error seems to be triggered from there. Any guidance on how to resolve this would be really helpful.
Error Details --
- Part of the query on scan_finding has been ignored because of insufficient access for 'query_range' operation on scan_finding.sys_created_on
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi @gopaljoshi
For this Error , Create a new ACL on scan_engine table - field sys_created_on
Set Role as per your requirement , make sure affected user is having that role.
Issue will be resolved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi @Tanushree Maiti
I have already created the query_range ACL and assigned both the sn_devops_ws.workspace_user and sn_devops_insights.user roles. But still it's not working. Same i have mentioned on my questions as well.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi @gopaljoshi
In our system , There are two role on Scan finding added by Servicenow.
Could you deactivate your custom ACL and try these 2. If working , update role as per your requirement.
scan_finding query_range ACL role : public
scan_finding.* query_range ACL role : public
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi @Tanushree Maiti
The issue is still not resolved, even after granting all DevOps-related roles in the ACL. The same roles are also assigned to the DevOps end user. Additionally, the public role has been added for the user, but the problem persists.
