Please attach a small sample survey (survey structure as .csv-file), where we can reproduce the issue - Thx!

I can reproduce the issue.

@ c_schmitz: I get the following notices working on the latest development revision at the second page of the survey:
Notice: Undefined variable: mandatorys in /home/.sites/962/site989/web/limesurvey/qanda.php on line 386

Notice: Undefined variable: mandatoryfns in /home/.sites/962/site989/web/limesurvey/qanda.php on line 386

Jason, that's totally not my area of expertise. Can you take a look at it?

I'm working on this now... Denniz, could you clarify what you mean by "It will be better to have the minimum and maximum answer attribute like a normal multiple options question." ? I don't really understand that bit.

I've removed the error messages, but the mandatory issue is a real problem. When the question type was developed it wasn't intended to have a checkbox. That was added on over the top. The checkbox means that every option is always answered. Not ticking a box means that zero is chosen - which the mandatory checking system considers to be a response. Coding around this would be quite a bit of work, since it will involve writing an exception to the normal rules. This is something I'm a bit loath to do since the checkbox feature as an addon to the base functionality (which works fine).

Hi Jason,

What I meant was having a attribute to limit the selection of answer. Just like the normal multiple-choice question type, you allow us to set what is the minimum and maximum answers the user can select.

With the minimum/maximum answer setting, then this question will become mandatory indirectly.

For example, with the minimum answer =1 AND max answer = 1, it'll then behave like a Radio question type, and 1 answer MUST be selected.

If users allow respondents to select as many as possible, then they just need to set the minimum answer =1 AND maximum answer = the # of options/answers available in the multiple choices. And this question is still mandatory because at least 1 answer MUST be chosen.

I hope this clarifies a bit, please let me know if this is still ambiguous.

Thanks!
Denniz

The mult-flexi (numbers) question type was never meant to be used as a multiple options replacement. The example you've provided is a misuse of the question type.

It is supposed to allow for a grid of questions/answers like this:

For each of the following indicate:
| I Like It | I Don't Mind It | I Hate It |
Cows | | | |
Zebras | | | |
Horses | | | |
Dogs | | | |

If you only have the one column, then you should use the multiple options question type.

If you have this grid, where for each of the animals, you have three options, then how do you decide whether a mandatory conditions has been met?

Jason

Hi Jason,

Yeah, I'm aware that multi-flexi(num) is not meant to be used as multiple-option replacement. However, because only Array question can utilize Array-filter to filter answers selected in previous question, so i used it as a workaround to behave like a multiple-option question, with only 1 label in Array.

If multiple-option quesiton/radio-list can have the ability to use Array-filter, then it would be really great.

Thanks!
Denniz

Please file a feature request instead, then.