Unable to initiate smart assessment for risk identification

[Ana41]

Hi all,

Hoping somebody can guide me through this. I am using smart assessments and trying to initiate a Risk Identification for some of my entities. I created a smart assessment with the assessment target Entity. I created a Risk Identification Configuration record mapping this questionnaire to my target entity class. However, when I create a Risk Identification record, I select the entity, click Save, and immediately get the following screen:

I have tried with several different assessments and several different entities but nothing seems to work. System logs don't show me anything. I even tried using only entities for which I am the owner, to no avail.

Can anyone help me understand what I'm doing wrong?

[Vinod54]

Hello @Ana41 ,

Could you elaborate on how you have triggered the smart assessment instance generation to the risk record. Is that through Trigger Smart Assessment Flow action. What are your scope item (table name) and how are you mapping the sys_id of the risk record? If these are set up correctly then, there should not be any issue in generating the smart assessment. 

For more information on Smart Assessment set up. Please feel free to read my community articles. 

What are the automation or scripting options available in Smart Assessment Engine? 

What is Smart Assessment Collaboration feature in the Smart Assessment Engine and how to implement? 

What is Smart Assessment Engine, how it is different from Classic Assessment ? 

Thanks,

Vinod Kumar M

[Ana41 · Accepted solution]

Replying to my own question in case anyone might find this useful: the problem was that the entity owners did not have the business_user_lite role. Since they had no GRC roles, they could not be respondents for the risk identification questionnaire, which caused the questionnaire initiation to fail.

Unfortunately the error message provided (as seen in the screenshot) is very generic and it was difficult to understand the root cause. I tested it using entities whose owners had at least business_user_lite privileges and it worked!