performance could be improved if not the survey_id was stored with the invitation but the survey_code
todo:
check if the user already filled the survey and if this is the case then the answers have to be updated and not stored again. alterantively we could not allow people from filling the survey twice.
performance could be improved if not the survey_id was stored with the invitation but the survey_code
todo:
check if the user already filled the survey and if this is the case then the answers have to be updated and not stored again. alterantively we could not allow people from filling the survey twice.