I am getting "there are no risk assessments defined for this request" error for all change request.

ShikhaPuri
Tera Contributor

I am getting "there are no risk assessments defined for this request" error for all change request, and not able to move to next state without calculating Risk assessment.
Can someone please help and suggest something to sort this issue ASAP.

8 REPLIES 8

Thanks mate for update. I am on latest release so not getting this error.

*************************************************************************************************************
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]

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

Hi @JHufford 

In regards to the part where you mention:

"After this fix, now you do need to at least put a condition value there for the assessment_conditions record to make sure the person who work on the change request could view the content of the risk assessment and proceed further."

Would you have more details?
We were just upgraded to Washington DC Patch 4 Hotfix 1b and it broke our change process. 
I was on vacation when they applied to our DEV/TEST instance and we missed the testing, now it's in PRD. ðŸ˜‘

That was really helpful, we just added a condition like:


Change Type IS Normal OR Emergency 

All good now!


You got it - i set the condition to active = true. Once that was set, I tested and the assessment opened fine

Hi. where is this condition added? We've tried to add it under assessment_conditions table as a new record like this 

Ahmet1_0-1729693505967.png

But its not working still getting the same error message? We've just had an upgrade and currently testing before production and this error is coming up in changes.