Unable to edit smart attestation

[Chenab Khanna]

Hi community,

I am exploring the Smart Assessment Engine within GRC and have created the attestation template along with the questions. Once the attestation is published, I am not getting an option to edit the template again or make it draft again if there are assessments existing for the template even if all are closed. 

I understand that the template should not be edited if there are open assessments associated but then we should have the option once all assessments are completed.

Anyone knows how to make the template back to draft to edit if we have assessments linked but all are completed?

[Ayush Aggarwal]

Hi @Chenab Khanna ,

Editing a template(For eg. Changing label of a question) would update the label of questions in all existing assessments(Open/Closed) and hence moving a published template to draft is prohibited if there are any assessments linked to a template. The only way you can move a published template to draft is deleting any assessments(sn_smart_asmt_instance) linked to the template. We will be providing features like template copy and template versioning in future to help the users. I hope this answers your question. Thanks.

[Chenab Khanna]

@Ayush Aggarwal thanks for your reply.

Do you have any published knowledge article supporting this for customer validity?

[Community Alums]

HI @Chenab Khanna ,

Making changes to a published attestation is not advisable.  But you can still do it if no other options to move forward. The attestation template fields are open and you get an "Update button" as well.

Can you share some screenshots as how are you creating the attestation templates please.

Also, @Ayush Aggarwal  is from ServiceNow, so you can consider his statement as an official statement for your customers for the proof.

[Christophe_E]

Hello Ayush,

Correct me if I'm wrong. For now, is it not possible to:

- copy an Assessment templates

- delete "sn_smart_asmt_instance"

- update a published Template

This means you cannot create an assessment, test it, and correct it if any defect on it as for testing purpose you'll create an assessment instance that cannot be deleted.

Is this right?