Bulk changing attestation respondents

[LJ3]

When staff leave, how can we bulk change the respondents on the attestations assigned to them?

I tried using the below script, but it does nothing unfortunately (even though it gives me a long list of re-assigned, it doesn't actually reassign):

var actualRespondentsSysID = '(currentusersys_id)';
var newRespondentsSysID = 'newusersys_id';
var gr = new GlideRecord('sn_compliance_control');
gr.addQuery('Respondents', actualRespondentsSysID);
gr.addQuery('state!=retired');
gr.query();
while (gr.next()) {
gr.Respondents = newRespondentsSysID;
gs.info('Control Attestation ' + gr.number + ' re-assigned');
gr.setWorkflow(false); // Optional: Do not run any other business rules (can only be executed in Global scope)
gr.update();
}

I can export the xml and replace the <respondents>SYID</respondents> then re-import, I've tested this but this isn't ideal if a user leaves who is the owner and attestation respondent to a lot of controls...

[Dexter Parre_o]

Jing is right. What he mentioned is the correct process when the attestation assignees need to be changed. You don't go into the attestation and change the Assigned To. You cancel it, set the correct profile owner (assuming this is where the attestation respondents are taken from), then put the controls back to Assess state. You can manage these bulk changes easier by creating list choices UI action in list view so that you don't have to go through each record separately.

[Prateek kumar]

You have to update this gr.Respondents = newRespondentsSysID; to the correct field name

Respondents doesn't look right. may be it is respondents ?

[marknyquist]

I've had luck with the following:

[Community Alums]

This script will only update the respondents but you are forgetting to cancel their attestations as well. The easiest way is to move the attestation to draft and attest again. 

[Community Alums]

Agree with jing, best practise should be to return control back to draft and re-attest with correct respondents. If you mark an entity as inactive, all risks all controls and respective attestations will be retired or cancelled because it works in cascade. (retire a risk or control and all attestations will be cancelled).

If you want to do it manually, you can inactive a profile and all controls/risks and respective attestations will be cancelled. I've tested and it works. If you want to check the code behind of this popup, check the link https://instance.service-now.com/sn_grc.DeleteDialogBox.jsdbx on your instance.