Why is control state not changing to 'attest' from 'review' or 'monitor' even if the scheduled job runs daily?

[avijeet]

Hi everyone,

Please help!

Even though in the scheduled job "Control attestation nightly run" which runs daily at 00:00:00 hours, according to it,   the controls in review/monitor state should return to attest state as per the frequency set. It is the OOTB(Out of the Box) functionality. But, currently it's not happening and the state of the control is not getting changed.

The script in   the scheduled job is :

var control = new GlideRecord("sn_compliance_control");

control.addQuery('state', 'IN', 'review,monitor');

control.query();

var now = new GlideDateTime();

while(control.next()) {

// Get the time of the last attestation

var attestationQ = new GlideRecord('asmt_assessment_instance_question');

attestationQ.addQuery('source_id', control.getUniqueValue());

attestationQ.orderByDesc('sys_updated_on');

attestationQ.query();

if(attestationQ.next()) {

var frequency = control.profile.attestation_frequency + '';

var lastAttested = new GlideDateTime(attestationQ.sys_updated_on + '');

switch(frequency) {

case 'daily':

lastAttested.addDaysUTC(1);

break;

case 'weekly':

lastAttested.addWeeksUTC(1);

break;

case 'monthly':

lastAttested.addMonthsUTC(1);

break;

case 'quarterly':

lastAttested.addMonthsUTC(3);

break;

case 'semi_annually':

lastAttested.addMonthsUTC(6);

break;

case 'annually':

lastAttested.addYearsUTC(1);

}

if(now >= lastAttested) {

control.state = 'attest';

control.update();

}

}

}

But the controls having frequency "daily" and in review/monitor state are not changing back to "attest" state after the execution of the scheduled job.

Please help and share anything that is needed more to accomplish this.

Regards,

Avijeet

[John Kelly1]

Hi Graham,

Thanks for sharing - I have been wondering about this as well.

The Profile form in Madrid no longer has the Frequency field visible and it does seem as though checking the Frequency on the Control table is more consistent with the design - why have the Frequency field on Control otherwise?

Looks to me as though ServiceNow might want to look at this again with a view to changing the scheduled job as suggested above.

thanks .. John