Risk assessment is not showing in SOW
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-24-2026 05:41 AM
Hi Team,
After Upgrade Risk Assessment is not showing in SOW, In Native UI it is showing in Related Link.
Any Help??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-24-2026 06:30 AM
Hi @Gopal14 ,
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!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-24-2026 10:00 AM
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
Risk Assessment related link not displaying
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
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