View Issue Details

This bug affects 1 person(s).
 6
IDProjectCategoryView StatusLast Update
07200Bug reportsSurvey takingpublic2013-01-29 12:44
Reporterhelper Assigned ToTMSWhite  
PriorityhighSeveritypartial_block 
Status closedResolutionno change required 
Summary07200: isEmpty logic at the question fails
Description

I have a question that looks at a previous group to check for an answer ((!is_empty(HH_SALT.NAOK) or HH_SALT.NAOK != "A1"))

The above is generated from the UI logic selector within the question.

Steps To Reproduce
  1. Import attached survey and navigate to the survey.
  2. Click on "Test this survey."
  3. Do not select any answers for the first group - just click on "Next"

Salt and sugary drink questions appear even thought he logic say not.

TagsNo tags attached.
Attached Files
Bug heat6
Complete LimeSurvey version number (& build)130116
I will donate to the project if issue is resolvedNo
BrowserChrome
Database type & versionmySQL
Server OS (if known)Windows 7
Webserver software & version (if known)Apache
PHP Version3.4

Users monitoring this issue

There are no users monitoring this issue.

Activities

helper

helper

2013-01-16 18:29

reporter   ~23698

Workaround: Edit the delete the defined set of logic created by the UI tool and insert the following:

((HH_SALT.NAOK != "" and HH_SALT.NAOK != "A1"))

c_schmitz

c_schmitz

2013-01-18 22:23

administrator   ~23712

Thomas, any idea?

TMSWhite

TMSWhite

2013-01-19 01:02

reporter   ~23717

Carsten-

The logic is properly generated from the Conditions editor and properly executed. HH_SALT.NAOK != "A1" will be true for any value that is not A1, including a non-answer.

In general, if you select multiple comparison options within a scenario for a condition, those options are always "OR"ed together. I don't recall any business rules that state they should be ANDed together (such as if you mix != and == comparisons).

So, to the best of my understanding, this is working completely as designed. As helper states, the workaround is easy - just specify the relevance directly instead of using the Conditions GUI.

FYI, I tested this on 1.92 and 2.0.

TMSWhite

TMSWhite

2013-01-24 06:07

reporter   ~23785

Per the note, this is working as designed.

c_schmitz

c_schmitz

2013-01-29 12:44

administrator   ~23888

New version 2.00+ Build 120129 released

Issue History

Date Modified Username Field Change
2013-01-16 16:42 helper New Issue
2013-01-16 16:42 helper File Added: limesurvey_survey_882993.lss
2013-01-16 18:29 helper Note Added: 23698
2013-01-18 22:22 c_schmitz Assigned To => TMSWhite
2013-01-18 22:22 c_schmitz Status new => assigned
2013-01-18 22:23 c_schmitz Note Added: 23712
2013-01-18 22:23 c_schmitz Status assigned => feedback
2013-01-19 01:02 TMSWhite Note Added: 23717
2013-01-24 06:07 TMSWhite Note Added: 23785
2013-01-24 06:07 TMSWhite Status feedback => resolved
2013-01-24 06:07 TMSWhite Resolution open => no change required
2013-01-29 12:44 c_schmitz Note Added: 23888
2013-01-29 12:44 c_schmitz Status resolved => closed