If someone completes the survey, the CallWeb QCOMP variable gets set to 1. The next time the process runs automatically/or is refreshed manually, their status will become “SurveyComplete” and the SURVEY_WINDOW_FLAG set to 1.
There can be instances when fielding the survey where a survey needs to be reset. This removes their responses and therefore their survey is no longer considered complete. When a survey is reset in CallWeb, QCOMP goes back to empty (i.e., not 1). But their status is not touched by the NJSA likely because it is considered a "final" state.
I think the "SurveyComplete" status should be more dynamic based on the result within the QCOMP variable. This status should either become Active or Expired based on where the individual is in the survey window.
For Future Update:
If someone completes the survey, the CallWeb QCOMP variable gets set to 1. The next time the process runs automatically/or is refreshed manually, their status will become “SurveyComplete” and the SURVEY_WINDOW_FLAG set to 1.
There can be instances when fielding the survey where a survey needs to be reset. This removes their responses and therefore their survey is no longer considered complete. When a survey is reset in CallWeb, QCOMP goes back to empty (i.e., not 1). But their status is not touched by the NJSA likely because it is considered a "final" state.
I think the "SurveyComplete" status should be more dynamic based on the result within the QCOMP variable. This status should either become Active or Expired based on where the individual is in the survey window.