| Description | USE CASE: Sometimes a respondent submits a survey, then contacts you to say they want to revise it.
ISSUE: In version 2.0 if you revise a response and associated token so that a user can have access again, the data are gone and a new response is generated rather than editing for the old response being enabled.
FEATURE: The feature request is that admins are given the ability to position responders on a particular page, only really useful when respondents are editing a previously entered questionnaire |
|---|
| Additional Information | MORE ABOUT WHY THIS WOULD BE USEFUL
In either case below, it would be nice to position the respondent on a particular page.
Alternatively there could be URL parameter that would tell the survey where to start.
1.92
In version 1.92 if you reset a respondents token and response to enable re-access, when they do so previously entered information is retained (good). However, upon returning to the survey respondents are positioned on the last survey page (sometimes bad). An issue arises when the last page is only shown for certain skip pattern conditions. In that case on reload the last page can't be shown due to skip patterns, so instead they are presented with the "Your survey is complete" page, which does NOT have a previous button.
The easiest solution for version 1.92 would be to give admins access to the lastpage variable for the response (added to the attached screen shot). That way if they want to change where surveys restart, they have access to that information. The only way I found around the issue was to export/modify/import the response information to set the lastpage variable.
Currently my work around for this issue is to add a final page with a text display letting that is not ever hidden because of skip patterns. Probably a good design principal anyway.
2.0
In version 2.0, if you reset respondents token and response so that they can re-access, when they do so a new response is generated, and the previously entered information is gone.
Haven't come up for any interim solutions for the issue of data being gone in version 2.0.
This is my first time reporting anything ... let me know if this is the kind of thing you want to see ... or not. |
|---|
