USEM Exception Management - Questionnaires

kenmcneil · 3 weeks ago

In USEM Exception Management when I click on "Vulnerability Response" under Basic Configuration ->Exception Management Configuration to select existing questionnaires the Select Questionnaire box is empty (no records to display) even though the Assessment Workspace shows they are there. This worked in VR, but no longer works after migration.

When I click on the filter for the Select Questionnaire box it says "Sys ID in"

Before I put in a support ticket I want to make sure that I am not missing a configuration setting. I checked with my SN team and I have admin access for USEM and all of the roles in the documentation.

TIA for your help

andy_ojha · 3 weeks ago

Hi @kenmcneil

Sorry we ran into this issue here.

I also saw this issue with the April 2026 release of VR (v30.3.3) in my lab

On that same instance, the issue was resolved with upgrading to the July patch release VR v30.7.2
Upgrading VR to the v30.7.2 also automatically upgraded the dependency Smart Assessment Engine (Smart Assessment Core) from 21.0.1 to 22.04 -> and then I saw the issue was resolved

Our Internal Team has confirmed that the issue is related to a dependency on the Smart Assessment Engine (Smart Assessment Core) Store App Version, and has updated the VR Compatibility (Store App) Matrix to reflect this.

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

We could directly upgrade the Smart Assessment Core Store App to 22.0.4 and it should address the issue here.

Alternatively, upgrading to the July patch release of USEM VR v30.7.2 will also take care of this (it will true-up the dependency here).

Sorry again this happened, @kenmcneil. I understand the friction this caused, disruption in time, and acknowledge these are quality and documentation improvement areas for us.

Reference - Reproducing in my lab with VR v30.3.3 (April 2026)

Reference - Relief after upgrading VR to v30.7.2

View solution in original post

kenmcneil · 3 weeks ago

Thanks everyone for your excellent responses. I am going to work with my team to implement @andy_ojha fix and will report back with the results.