You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes, multiple case workers collect various surveys and save, but do not submit, them. Then, a manager may submit all the saved surveys at once. The user id would then be the manager, and not the actual surveyor. So, we would like to add to the APIs a "SurveyorID"/"AdministeredDate" which would track the original person performing the survey, not necessarily the same as the the user finally submitting. AdministeredDate would track when the surveyor actually administered the survey, not the date uploaded.
Sometimes, multiple case workers collect various surveys and save, but do not submit, them. Then, a manager may submit all the saved surveys at once. The user id would then be the manager, and not the actual surveyor. So, we would like to add to the APIs a "SurveyorID"/"AdministeredDate" which would track the original person performing the survey, not necessarily the same as the the user finally submitting. AdministeredDate would track when the surveyor actually administered the survey, not the date uploaded.
cc: @CTAJavier
The text was updated successfully, but these errors were encountered: