Valid to date issue

Dhruv Gupta1 · ‎08-12-2020

Hi team,

Consider a scenario where someone has raised a policy exception with all valid values and it has been sent for approval and its waiting for the approval and in between the valid to field expires. Then if someone approves a policy exception will the policy exception will move forward or not.

I tried but its keep on giving the valid to should be in future kind of error and we can't proceed further. Here the user has raised the exception and its approved but due to valid to field getting expired before exception getting approved its stuck.... and state is not getting changed to approved so that workflow could trigger. Is it a feature or a bug!!

Regards

Dhruv

Phil Swann · ‎08-14-2020

@Dhruv Gupta I know we spoke on this briefly.

It seems a question of very short timeframes on a PER. If that is the case, I think you need to look more at how you can support the behaviours not bypass the process. Are the approvers having trouble? Are the requesters requesting things too late, or with too little notice?

In change management, the concept of 'retrospective change' exists. In PER , is an approval received for something in the past not a similar thing? A record of something.

PER was built to help organisations provide temporary relief for any control(s). This means in material terms that those controls will be marked compliant/exempt and attestation will be bypassed. Once closed, the control will revert back and if the issue is still open, will be non-compliant again. If it was an attestation issue and you re-attest (automatically) and the issue is still open, the successful attestation will set the control back to compliant and close the issue.

Trying to alter this approval and overall behaviour is dangerous. PER has just had a really good lick of paint in v10.1 and making changes to any core flows will certainly increase complexity and risk in future upgrades.

Happy to discuss more, hope this helps and thanks for reaching out!

View solution in original post

Sajilal · ‎08-12-2020

Hi,

This should not be a bug but a OOB behaviour, ideally for the policy exception which is raised "valid to" field highlights the Day on which the policy exception would actually end. Therefore you will have to change the date on the valid to in future to proceed.

Please Mark as ✅ Correct if this solves your issue and also mark ???? Helpful if it helps resolve your problem.

Thanks,
Saji

Dhruv Gupta1 · ‎08-13-2020

Suppose you say I want a policy exception starting from today till tomorrow and i raised an exception, Now the approver approves one day after the valid to date passes. Now it will be stuck and also user can't raise the same exception because now both the dates will be past dates !!

So now what is expected from user as in user will say hey it is approved and I only want exception for that duration and I raised it before it becomes a past date!!

Sajilal · ‎08-14-2020

Hi Dhruv,

If its a concern with the OOB behaviour, you can modify the valid to date logic accoringly. So basically a scenario if the policy exception was for 1day, then as soon as your approver approves it, move the Valid to date to 1 day from that particular day. Or any other customization is possible.

Please have a word with the Hi Servicenow as well if required and perform modification to the OOB feature.

Please Mark as ✅ Correct if this solves your issue and also mark ???? Helpful if it helps resolve your problem.

Thanks,
Saji

Keval Parikh1 · ‎08-13-2020

Hi Dhruv,

I'm also currently working on the Policy Exception module. We're also facing the same issue. Ideally your extension should approved before your actual "Valid To" date. If not, then your PE record will be "Closed" and you're no longer able to take any actions on that PE record. You have to start from the scratch. For an example, if your PE is expired 7 days back and your extension approved today, what about these 7 days? For this specific time period your control(s) will be in "Non-Compliant" State.

According my understanding, you can consider this as feature of the ServiceNow, However, you can improvise this feature with slight modifications in the OOB workflow, as it not always possible scenario with the OOB workflow of the ServiceNow.

Thanks,

Keval