How do you cancel a survey in "ready to take" state, when it is not in the active contexts workflow list?

[paw2]

I have some surveys in the "ready to take" state that need to be canceled.  According to ServiceNow docs, you should be able to go to the active contexts workflow and select it and then cancel it.   However, none of these are listed in the active contexts module.

Kingston patch14

[Allen Andreas]

Hi,

I'm not sure about where the documentation says to go to active workflow context for these, but the way surveys work is that once the due date passes, it will be eligible to be cancelled the next time your scheduled job called: "Cancel Expired Assessments" runs (which is once every 30 days). So, in essence, you'd have to change the due date (which OOB the field is read only - so you'd need to do this via background script or uncheck the read only parameter, change it, then put it back) then....go to scheduled job and perhaps force it to run right now.

The job I'm referring to is found within the: System Scheduler > Scheduled Jobs > Cancel Expired Assessments

Please mark reply as Helpful/Correct, if applicable. Thanks!

[paw2]

Thanks Allen,  all good ideas.  I thought about changing the due date, but my attempt to do that via changing the duration field did not change the date.  I bet your idea would work to do it that way.  I found a faster way for small number of survey change. 

The Cancel Expired Assessments would be good to copy and modify to include several survey changes at once, though.

[paw2]

Here is another slick way to cancel without having to script, if you have a small number of surveys to cancel.  Open the survey and export to xml.  Change the state to the value of the state field.  Save it.  Back out of the survey to the list view, and right click between the hamburgers in the list.  At the bottom, select import xlm.

[Allen Andreas]

Hi,

Interesting in small doses...haha.

If my post above solved your issue, please mark it correct so that others can find it easier.

Thanks and glad you got your issue resolved! 🙂