After the latest Washington Patch Hot Fix 2 update, Release managers no longer can create release

User338031
Tera Contributor

 

After the latest Washington Patch Hot Fix 2 update, Release managers no longer can create release.

 

Error message: "Part of the query on rm_release has been ignored because of read security rules on rm_release.sys_class_name" (screenshot attached)

 

As an admin I am able to create releases but release admins. I have checked their permissions and nothing has changed compared to the previous version of patch. I am unable to find any new security rules as well. 

 

Any immediate help appreciated.

 

Thank you,

Neeraj

 

 

 

4 REPLIES 4

Dr Atul G- LNG
Tera Patron
Tera Patron

Hi @User338031 

 

The prime reason, the plugin is not activated correctly, please try to repair the plugin once.

 

If still not work , try to create a new user and give only RM roles and check.

 

else, log  a Now support case.

 

FYI - In D.C. Release SN has introduced new application, called Digital Product Release.

 

https://youtu.be/OjLdfawvBZI

 

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************
The latest Application, DPR, was launched by SN in D..C. Release. A quick demo of same is available here.

User338031
Tera Contributor

Hi Atul,

 

Thank you so much for your response! I had opened a support case and we were able to solve the issue.

The reason was that the user level ACLs were working fine but the field level ones were failing because "Explicit roles" plugin was not installed in the QA instance. So, either you add the required role manually to the user/group or install the plugin to fix the issue.

 

Thanks again!

Wow.. good to know.. @User338031 

 

Please accept the required answer as solution and close the thread.

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************

Balaji M
ServiceNow Employee
ServiceNow Employee

Hi @User338031 

This issue caused due to this ACL : sys_security_acl.do?sys_id=735fd39a9f710300a3e75bb0657fcf8c and it has been fixed in this version : Washington DC patch 3.

So please upgrade your instance to the fixed version.