Closed VITs in deferral state when re-opened do not defer

[Teena H]

From what I understand: Vulnerabilities which are deferred using an exception rule, if they close and then open whilst deferred no longer retain the deferred status and move to open. 

I believe from reading the forums this is as designed and there is another question someone posed here which indicated this is as intended: https://community.servicenow.com/community?id=community_question&sys_id=7c2ba2c3db090d10dd886c8e1396...

And a linked feature request which I have upvoted.

However I still have an issue where the business is expecting these vulnerabilities to remain deferred even when they re-open until the deferral end date. Has anyone else experienced this and has anyone come up with a workaround to meet the business expectation? (eg, is there a script/rule/configuration we can change to work around this problem?)

[Stephen Laseau]

I had to deal with the same requirement.  You do not want to add a BR to the vulnerable item table.  Instead, create a scripted scheduled job that runs each AM to review all VITs updated yesterday, that are open, to determine if there is an associated exception so you can update accordingly.  This approach succeeded.

[Teena H]

Why do you say no business rules?

[Chris McDevitt]

Hi,

This is how I solved this for a few large customers:

https://community.servicenow.com/community?id=view_idea&sysparm_idea_id=3ab7c5cc1bbec150d018c8ca234bcb7d&sysparm_idea_table=x_snc_com_ideation_idea&sysparm_module_id=enhancement_requests

[son1]

Hello,

the link you have provided is not working, do you have any other link that would work?

appreciate it