Deactivate or delete a Remediation Effort?

PJS_DFS
Tera Contributor

Could someone please guide me on how I can "delete" or "deactivate" a Remediation Effort?

 

It seems according to ACLs, no one can delete an effort, even Admins.  But it appears there should be a way to deactivate one, but it is all grayed out.  Are there certain rights I would need?  I am a VR Admin in my instance.

PJS_DFS_0-1713278760255.png

 

3 REPLIES 3

Abhinav37
ServiceNow Employee
ServiceNow Employee

Hi, 

Based on the field ACL (write) on the "active" field on the sn_vul_remediation_effort table, users with the granular role "sn_vul.edit_effort" can edit this field. This field is contained both by the sn_vul.vulnerability_admin & sn_vul.vulnerability_analyst roles. So essentially users with either of these roles should be able to edit this field.

 

Screenshot 2024-04-19 at 1.32.57 PM.png

 

But however, the "Active" field is set to read-only by default in sys_dictionary which negates the above ACL and no one can update the active field.

Screenshot 2024-04-19 at 1.33.26 PM.png

And finally based of this ServiceNow docs page,

"A Remediation Effort is deactivated automatically when there are no active records."

 

So essentially when all the remediation tasks and VITs have been closed/ set to inactive the remediation effort gets deactivated automatically. I did not test if this happens, but am sure this should be the behaviour.

 

Hope this helps.

Thanks!

Makes sense.  But I have been messing around with Remediation Efforts to test things.  Created a bunch of Remediation Tasks within it.  But then wanted to start over again.  I deleted all the tasks, but there is still 27K VITs associated with the efforts.  I just wanted to find a simple way to close the Effort.

 

I see I can modify the Is a Part of a Remediation effort field, but doing that for 27K records will be CRAZY.  Would be wonderful if it could be simplier.

Abhinav37
ServiceNow Employee
ServiceNow Employee

Yeah that does sound crazy, Probably you can play around with the Update All functionality or write a fix script :), Ill check if there's any other way to achieve this.