Interested in a ServiceNow event built for developers? Registration for now[dev]26 is officially open!

Why assessor or requestor fields are not present in smart assessment records?

testhhh123
ServiceNow Employee

We wanted to show assessor and requestor in the list view of smart assessments but I cannot find those fields in the records.

1 ACCEPTED SOLUTION

Dan_Junqueira
Tera Contributor

Hey Steven how are you? 

Smart Assessments use a slightly different data model from traditional ServiceNow assessments.

The assessor is not stored as a simple field on the assessment record because the engine supports multiple users and personas. The assessor information is maintained through the assessment-persona-user relationship.
The requester is provided as part of the assessment creation/trigger context.

So, if we want these values available directly in a list view, we may need to expose them through the related tables or create/report on a derived field rather than expecting standard Assessor and Requester fields on the assessment record.

Follow this article from ServiceNow maybe can be usefull

https://www.servicenow.com/docs/r/governance-risk-compliance/smart-assessment-engine/tables-installe...

In ServiceNow Smart Assessments, the assessor and requester are not modeled as simple fields directly on the assessment record because the Smart Assessment Engine supports multiple participants and personas. The assessor relationship is maintained through the Assessment Instance to Persona to Users table (sn_smart_asmt_m2m_instance_persona), which allows an assessment to have different users assigned to different personas, such as assessor or reviewer.


If my answer was helpful, please consider marking it as useful. I’d really appreciate your feedback.

Dan Junqueira

View solution in original post

1 REPLY 1

Dan_Junqueira
Tera Contributor

Hey Steven how are you? 

Smart Assessments use a slightly different data model from traditional ServiceNow assessments.

The assessor is not stored as a simple field on the assessment record because the engine supports multiple users and personas. The assessor information is maintained through the assessment-persona-user relationship.
The requester is provided as part of the assessment creation/trigger context.

So, if we want these values available directly in a list view, we may need to expose them through the related tables or create/report on a derived field rather than expecting standard Assessor and Requester fields on the assessment record.

Follow this article from ServiceNow maybe can be usefull

https://www.servicenow.com/docs/r/governance-risk-compliance/smart-assessment-engine/tables-installe...

In ServiceNow Smart Assessments, the assessor and requester are not modeled as simple fields directly on the assessment record because the Smart Assessment Engine supports multiple participants and personas. The assessor relationship is maintained through the Assessment Instance to Persona to Users table (sn_smart_asmt_m2m_instance_persona), which allows an assessment to have different users assigned to different personas, such as assessor or reviewer.


If my answer was helpful, please consider marking it as useful. I’d really appreciate your feedback.

Dan Junqueira