'Save' button on 'Risk Workspace' unable to save inherent risk assessment responses entered by user

[Abhinandan Pati]

Hello Community,

As shown in the below image I have an issue with the 'SAVE' button on 'risk-assessment-main' page of 'Risk Workspace'. 'Save' button on inherent risk assessment page is unable to save responses of factors  that are defined for Risk Assessment Methodology.

But same functionality works in the native UI of ServiceNow. We have this issue only in Risk Workspace. We can view the responses entered using native UI but we can not save the risk assessment responses using Risk Workspace UI.

I tried to debug this issue by checking in below tables but could not find the configuration of 'Save' button. 

1. UX Client Script: sys_ux_client_script
2. UX Page Registry: sys_ux_page_registry
3. UX App Routes: sys_ux_app_route
4. UX App Configurations: sys_ux_app_config
5. UX Screen: sys_ux_screen
6. UX Macroponent Definition: sys_ux_macroponent
7. UX Page Properties: sys_ux_page_property

Is '/api/sn_risk_advanced/riskasmntapi/saveFactorResponses' REST API being used anywhere to save the responses? Please share your thoughts if you have encountered similar issue anytime.

Thanks,

Abhinandan

[Abhinandan4 · Accepted solution]

This issue is fixed by upgrading ‘GRC: Advanced Risk Assessment’ store application to its latest version: 14.2.0.

ServiceNow raised change request to upgrade store application 'GRC: Advanced Risk Assessment’ to its latest version. Only maint user can upgrade this application. You can find this application in 'sys_store_app' table.

Please refer attached article for more information

Unable to save risk assessment response on the risk assessment form in workspaces - Known Error - No...

[Abhinandan Pati]

Upgrading 'GRC: Advanced Risk Assessment’  to latest version will fix the issue only if ServiceNow instance is on 'San Diego' version. This fix wont work if ServiceNow instance is on lower versions. ServiceNow does not recommend upgrading this plugin if ServiceNow instance is not on San Diego version. ServiceNow confirmed the same in one of support ticket that I raised. Here are the details from support ticket.

As we mentioned in our previous update, the instances should be upgraded to San Diego and there is no other workaround is available

The problem comes from the GRC: Advanced Risk Assessment 14.2.0 being only compatible with the San Diego release as explained in GRC: Advanced Risk Assessment 14.2.0

This in turn is because the GRC: Risk Management Workspace 14.1.2 is only compatible with the San Diego release as explained in GRC: Risk Management Workspace 14.1.2

The GRC: Risk Management 14.1.1 is compatible from Quebec to San Diego but only when used as standalone without the workspace. GRC: Risk Management 14.1.1

In conclusion you should not try to install the version 14 in your environment before you upgrade in San Diego.

Please let me know if this clarifies the situation and answers your issue.