Attestation Frequency

[marknyquist]

I have a few controls, where the attestation frequency is set to 'none', but after the attestation recipient completes the form, the nightly scheduled process sets it back to Attest. (Activity journal shows Administrator, System - State  Attest was Review). 

I have an open HI ticket, but am hoping the community might have a faster answer. 

I had assumed that controls would not be affected by the scheduler until they were in a 'monitor' state? I set up controls that had an indicator template to 'none' since after the first attestation, we could reply on the indicator frequency to show the control was still operating. 

Has anyone seen this behavior before?

Thanks in advance!

Mark

[Phil Swann]

Are you in New York?

Just check this one: https://community.servicenow.com/community?id=community_question&sys_id=6dafb00fdb4a5f844837f3231f961913 

I don't think it applies. That sounds wrong.

Controls will be picked up by the job in both Review and Monitor.

Regarding replacing those with an Indicator to none, I think this is OK if you are comfortable but it might still be good to have some kind of manual intervention just to check everything is still valid, especially ownership. Attestation can be good for keeping those things in check, and indicators can help to demonstrate continuous alignment. 

[Khang1]

Hi Mark,

From my experience and understanding, the Attestation Frequency is set at the Entity level and not the frequency field in Control record; see pic below. So, if you open the entity that a control is belong to, you can see the attestation frequency set for all downstream controls in that entity.

From the behavior described, maybe the attestation frequency is set to 'Daily' in the control entity by mistake? Anyways, there's a daily job that check for the attestation frequency in the entity, then check the last time the downstream controls is attested to. If the frequency threshold is reached from last attestation, it will automatically move the control to 'Attest' stage.

The only way to prevent auto attestation (if you have manual attestation process in place) is to disable the nightly job (make sure to NOT remove it). The job is under 'System Definition>Scheduled Jobs' called, "Control attestation nightly run".

[marknyquist]

Thanks for the helpful advice so far. In my testing, when I set the control attestation frequency to something other than 'none', it does not regenerate, so I think the frequency is at the control level and not the entity. In addition, I looked at the scheduled job which calls the ControlAttestationUtilsBase script, and it looks like it will always set the control back to attest, it's just a matter of when. If no value is entered, it's immediate. I will wait for HI to reply and also ponder just putting in a condition in the script that won't reset the control state if no frequency is specified. I will certainly post back if I hear something otherwise. 

[marknyquist]

In case it helps anyone, the following was confirmed by HI support:

Any control with a frequency of ‘none’ and a state of 'review or monitor' will have the status set back to ‘attest’ at each time the ‘Control attestation nightly run' occurs.