Interested in a ServiceNow event built for developers? Registration for now[dev]26 is officially open!

Risk assessment is not showing in SOW

Gopal14
Tera Contributor

Hi Team,

 

After Upgrade Risk Assessment is not showing in SOW, In Native UI it is showing in Related Link.

 

Any Help??

3 REPLIES 3

Huynh Loc
Mega Sage

Hi @Gopal14 ,

Please refer to the following ServiceNow Knowledge Base article for detailed information on this issue:

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2190948

 

If this response was helpful, please consider marking it as Helpful and/or Correct.
You may mark more than one reply as an accepted solution.

Thanks!

Tanushree Maiti
Tera Patron

Hi @Gopal14 

 

By design there is no UI Action 'Risk Assessment' on Change Request in Service Operation Workspace. Instead the functionality to re-run risk assessment is provided in the side panel of Change Request in Service Operation Workspace.

 

Refer:

Change management in SOW, Assess Risk button not working 

Risk Assessment UI action missing on the form 

Why there is no 'Risk Assessment' option available for Change Requests in Service Operations Workspa... 

Risk Assessment related link not displaying 

 

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti

jknights
Tera Contributor

Hi @Gopal14,
I don't know if you are still having this issue but we had the same issue happen after the Australia upgrade.
The fix steps we found was:
1. Head to Change -> Workspace Configuration -> Overview Card 
2. In the 'name' field search for 'Risk' and 'heading' field 'Risk evaluation' and open it
3. Once opened removed the display condition.

It seems the display condition was changed in the Australia updated and in the code for the 'Chg Overview Risk SNC' I could see that the UX display event and API 'api.data.risk_evaluation_change.output.riskActions.showChangeRiskDetails' is no longer called so I think they have moved from this API call and added the display condition instead.

Good luck!
Jake