Written by tpartner the 19 Dec 09 at 01:08.

To toggle the questions to optional, the button would query the DB, find all questions in the current survey with mandatory=Y and change them to mandatory=M.

We need to use "M" so we can find them to toggle them back later.

The system would see "M" as non-mandatory so all of these questions could now be skipped in a Q/A process.

This way only the questions that the survey author had set to mandatory would be affected.

To toggle the questions back to mandatory, the button would query the DB, find all questions in the current survey with mandatory=M and change them to mandatory=Y.

I've put together a little php script to demonstrate the concept that you can grab at http://partnersinc.biz/testsites/misc_images/mandatory_toggle.txt (can't seem to attach anything here!).

To toggle the questions to optional, the button would query the DB, find all questions in the current survey with mandatory=Y and change them to mandatory=M. We need to use "M" so we can find them to toggle them back later. The system would see "M" as non-mandatory so all of these questions could now be skipped in a Q/A process. This way only the questions that the survey author had set to mandatory would be affected. To toggle the questions back to mandatory, the button would query the DB, find all questions in the current survey with mandatory=M and change them to mandatory=Y. I've put together a little php script to demonstrate the concept that you can grab at http://partnersinc.biz/testsites/misc_images/mandatory_toggle.txt (can't seem to attach anything here!).

Written by tpartner the 19 Dec 09 at 14:40.

A more elegant solution may be to have the button/input set a session variable to disable the "checkmandatorys" function. (thanks Carsten)

Some red text could then be displayed at the bottom of the survey indicating that it is in "Q/A" mode and all questions are optional.

A more elegant solution may be to have the button/input set a session variable to disable the "checkmandatorys" function. (thanks Carsten) Some red text could then be displayed at the bottom of the survey indicating that it is in "Q/A" mode and all questions are optional.

Written by lwc the 17 Nov 10 at 19:35.

Give the users a summary of all their answers, and force them to approve it in order to submit the survey.

Of course, make it an on/off option so each admin could decide whethere to force it or not.

Give the users a summary of all their answers, and force them to approve it in order to submit the survey. Of course, make it an on/off option so each admin could decide whethere to force it or not.

Written by andrewteg the 19 May 11 at 17:21.

Much like you have INSERTANS, I propose an INSERTQUESTION replacement field. Then you can at least setup a dynamic Question and Answer review page using a boilerplate field. This is not as convenient as a full review question page/type option, but would allow someone to setup a review page without having to retype the question text.

A quick button to spit out all of them would be pretty great too.

Much like you have INSERTANS, I propose an INSERTQUESTION replacement field. Then you can at least setup a dynamic Question and Answer review page using a boilerplate field. This is not as convenient as a full review question page/type option, but would allow someone to setup a review page without having to retype the question text. A quick button to spit out all of them would be pretty great too.

Written by apps the 5 Feb 10 at 14:10.

Add a button to the survey button bar, next to "Token management"
Create a page to review all conditions in the current SurveyID

Add a button to the survey button bar, next to "Token management" Create a page to review all conditions in the current SurveyID

Written by mmaa the 18 May 10 at 18:49.

check each placeholder if it's empty and if so place a string like "no answer given"

check each placeholder if it's empty and if so place a string like "no answer given"

Written by Mazi the 23 Oct 09 at 16:24.

Solution for 1.
A) If $debug is set to "2"/"3" don't execute the mandatory check.
B) New config setting "$ignore_mandatory", if set to "1" don't execute the mandatory check.

Solution for 2.
A) Create a "All questions are mandatory?" -> yes/no option at survey settings
B) Create an overview which lists all questions and a simple "mandatory yes/no" radio option. This way you can set up your survey without making question mandatory from the beginning at chose which questions should be mandatory at a later step.
This overview can be survey or group based.

Solution for 1. A) If $debug is set to "2"/"3" don't execute the mandatory check. B) New config setting "$ignore_mandatory", if set to "1" don't execute the mandatory check. Solution for 2. A) Create a "All questions are mandatory?" -> yes/no option at survey settings B) Create an overview which lists all questions and a simple "mandatory yes/no" radio option. This way you can set up your survey without making question mandatory from the beginning at chose which questions should be mandatory at a later step. This overview can be survey or group based.

Written by GregB the 16 Feb 10 at 23:28.

It would seem to me that someone very smart person could make some script to convert survey data into mindmap data.

This would be a straight export from LimeSurvey to the mindmap data structure.

Branches can be colorcoded to denote conditions.

It would seem to me that someone very smart person could make some script to convert survey data into mindmap data. This would be a straight export from LimeSurvey to the mindmap data structure. Branches can be colorcoded to denote conditions.

Written by holch the 5 Mar 10 at 18:59.

I agree that the MindMap Structure wouldn't really work.

But I know some survey tools, that use a kind of "folder structure" as we know it from file explorers, etc.

I think this can display filters and so on pretty well. At the moment Quotas, Filters, and questions are somehow displayed very seperate and it difficult to get a good overview of the survey (I do agree with the GregB here).

But with the folder tree, you can show loops, filters, pages/groups and questions, which can be especially helpful for long and complicated surveys.

I agree that the MindMap Structure wouldn't really work. But I know some survey tools, that use a kind of "folder structure" as we know it from file explorers, etc. I think this can display filters and so on pretty well. At the moment Quotas, Filters, and questions are somehow displayed very seperate and it difficult to get a good overview of the survey (I do agree with the GregB here). But with the folder tree, you can show loops, filters, pages/groups and questions, which can be especially helpful for long and complicated surveys.