Find your people. Pick a challenge. Ship something real. The CreatorCon Hackathon is coming to the Community Pavilion for one epic night. Every skill level, every role welcome. Join us on May 5th and learn more here.

DevOps Change Workspace Home page error

gopaljoshi
Tera Contributor

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



gopaljoshi_0-1777311043078.png

 

7 REPLIES 7

Tanushree Maiti
Kilo Patron

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. 

 

TanushreeMaiti_0-1777322236261.png

 

 

Issue will be resolved.

 

 

Please mark this response as Helpful & Accept it as solution if it assisted you with your question.
Regards
Tanushree Maiti
ServiceNow Technical Architect
Linkedin:

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.

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

Please mark this response as Helpful & Accept it as solution if it assisted you with your question.
Regards
Tanushree Maiti
ServiceNow Technical Architect
Linkedin:

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.