We're reclaiming inactive PDIs to keep them available for active builders. Learn what's changing, who's affected, and how to protect your work. Read More

Issue while creating ad-hoc risk in risk assessment project, when risk statement in populated

poojithaven
Tera Expert

3 weeks ago - last edited 3 weeks ago

while creating ad-hoc risk in risk assessment project, when risk statement in populated and clicked on save, The screen gets stuck on save and no error message is displayed. Anyone else faced this issue, any solution by proposed ServiceNow?

poojithaven_0-1783000068363.png

 

0 Helpfuls
  • 465 Views
1 REPLY 1

Vikram Reddy
Tera Guru

a week ago

Hi @poojithaven,

 

Nine times out of ten this is the OOB duplicate check on the risk base table kicking in, not a genuinely broken Save button. As soon as the Risk Statement you pick resolves to an Entity + Risk Statement combination that already exists somewhere in the system, the "Enforce Unique Item" business rule on Control/Risk (sn_grc_item) aborts the insert. The catch is that the ad-hoc "Add risk" panel inside a Risk Assessment Project is a Risk Management Workspace panel, not the classic form, and that panel doesn't reliably render the business rule's abort message as a toast. So instead of an error you just get a spinner sitting there forever.

  1. Open dev tools, go to the Network tab, and click Save again. If it's the duplicate check, the failed insert response (against sn_risk_risk / sn_grc_item) will actually contain the "risk with the same Entity and Risk Statement already exists" text, even though nothing shows up on screen.
  2. Check whether a risk already exists for that same Entity (ACME CD Europe in your screenshot) against that same Risk Statement. Your Risk Statement text matches the Name and Description exactly, so it's worth checking if that statement is already linked to that entity from an earlier scoping or assessment pass.
  3. If you genuinely need a second risk instance against the same entity and risk statement, uncheck Sync with entity owner is unrelated, what you actually want is the Inherit from risk statement flag on the risk record. Turning that off lets the risk statement act as a categorization hierarchy instead of a strict 1:1 link, so multiple risks can point to the same entity/risk statement pair.
  4. If there's no duplicate and that flag is already off, rule out an outdated store app before anything else: check the versions of GRC: Advanced Risk Assessment and Risk Management Workspace. ServiceNow has shipped fixes for near-identical "save hangs, no error shown" behaviour in the risk assessment scripted REST layer through store app upgrades rather than platform patches, so it's a quick thing to eliminate.

One thing that would narrow this down fast: can you save that same Entity/Risk Statement pairing from the classic Risk list form directly, outside the assessment project workspace? If that works fine, it confirms it's the workspace panel swallowing the error rather than the duplicate rule itself.

 

Thank you,
Vikram Karety
Octigo Solutions INC

0 Helpfuls