'Event mapping target action is undefined (for elementId = get_data_for_start_assessment_1)' error on Risk Assessment Page of Risk portal

[Abhinandan Pati]

Hello experts,

I am getting below errors in console of a browser on click of 'Lets get started' button of Risk Assessment. This issue is only for users with a role: 'sn_risk.user' and 'sn_risk.manager'. I don't have the same issue for 'admin' users. Risk Assessment moves to 'Assess' state on click of 'Lets get started' button for admin users but same is not the case for Risk managers and Risk users

'Event mapping target action is undefined (for elementId = get_data_for_start_assessment_1)'

ServiceNow instance is on Rome version and below is the list of plugins and their versions. I raised ServiceNow HI ticket for this issue and ServiceNow support team suggesting us to upgrade the instance to San Diego version and upgrade all below store applications to their latest version to fix this issue. As per ServiceNow support team there is no workaround for this issue in Rome version. Currently we don't have plans to upgrade our instance to San Diego version. 

GRC: Advanced Risk                            14.2.3
GRC: Advanced Risk Assessment        13.0.5
GRC: Risk Management                       14.1.1
GRC: Risk Management Workspace    13.0.4

Suspecting access issue, I provided write access of 'Risk Assessment' table to sn_risk.user , sn_risk.manager and also added these 2 roles to OOB REST_Endpoint ACL: 'Risk assessment scripted rest end point', which is associated with 'Copy previous assessment responses' method of OOB Scripted REST API: 'riskAsmntApi'. But configuration of ACLs did not help to fix this issue.

I see that 'get_data_for_start_assessment_1' is being used in few client scripts of UI builder. Please refer below snapshot. But I could not find out the source script of element: 'get_data_for_start_assessment_1'

Did anyone face similar issue? How did you resolve it? Please let me know if you fixed similar kind of issue anytime.

@Jan Spurlin @Phil Swann @Pranav Bhagat @Rafael Cardoso @Shiva Thomas @Ankur Bawiskar @Chuck Tomasi @Ashley Snyder @Ashley Snyder : Please share your inputs if you have any idea regarding this issue.

Thanks,

Abhinandan

[Phil Swann]

Your versions are out of sync. Running v14 of the apps with v13 of the workspaces will have unintended results, and unsupported behaviour. Looks like you found a solid example of why these versions should not be mixed! 

Upgrade to San Diego, then upgrade the apps to v14 ! 

[Abhinandan Pati]

Thanks Phil for your inputs.

[Aman18]

Hi @Abhinandan Pati 

Did you find the cause and solution?

Thanks,

Aman Giri

[jaikishan1]

Hi @Aman18 ,

The issue happens due to mismatch of release versions between dependent applications. All the dependent applications should be on the same release versions to avoid any such issues.

Please mark this answer as helpful if it resolves your query.

Regards,
Jai