Setting conditions - Revision history

Joeyh278 at 00:58, 27 February 2024

2024-02-27T00:58:00Z

← Older revision		Revision as of 02:58, 27 February 2024
Line 718:		Line 718:


	===How to use ~~parenthesis~~ for the boolean expressions?=== <!--T:173-->		===How to use parentheses for the boolean expressions?=== <!--T:173-->

C schmitz: Text replacement - "Check the following" to "Check out the following"

2020-10-18T17:12:01Z

Text replacement - "Check the following" to "Check out the following"

← Older revision		Revision as of 19:12, 18 October 2020
Line 86:		Line 86:

	<!--T:192-->		<!--T:192-->
	{{Note\|Check the following [[Question types\|link]] to find out more about the available question types in LimeSurvey.}}		{{Note\|Check out the following [[Question types\|link]] to find out more about the available question types in LimeSurvey.}}

	<!--T:24-->		<!--T:24-->

Cdorin at 08:27, 15 April 2020

2020-04-15T08:27:39Z

← Older revision		Revision as of 10:27, 15 April 2020
Line 21:		Line 21:

	<!--T:238-->		<!--T:238-->
	{{Hint\|Text=The conditions functionalities work like a GUI for [[ExpressionScript\|the expressions and equations that can be applied to questions]], allowing the users to easily increase the complexity of their surveys without getting into expressions and relevance equations. However, [[ExpressionScript\|the ExpressionScript]] must be studied/known to increase the range of options that is available within LimeSurvey.}}		{{Hint\|Text=The conditions functionalities work like a GUI for [[ExpressionScript - Presentation\|the expressions and equations that can be applied to questions]], allowing the users to easily increase the complexity of their surveys without getting into expressions and relevance equations. However, [[ExpressionScript - Presentation\|the ExpressionScript]] must be studied/known to increase the range of options that is available within LimeSurvey.}}


Line 292:		Line 292:

	<!--T:42-->		<!--T:42-->
	* a ''comparison operator''. Choose the ''comparison operator'' you want to apply from the dropdown list (''less than'', ''less than or equal to'', ''equals'', ''not equal to'', ''greater than or equal to'', ''greater than'', ''[[ExpressionScript\|regular expression]]'').		* a ''comparison operator''. Choose the ''comparison operator'' you want to apply from the dropdown list (''less than'', ''less than or equal to'', ''equals'', ''not equal to'', ''greater than or equal to'', ''greater than'', ''[[ExpressionScript - Presentation\|regular expression]]'').


Line 563:		Line 563:

	<!--T:261-->		<!--T:261-->
	<div class='simplebox'> [[File:help.png]] '''Help:''' For more information on relevance equations, check the [[ExpressionScript]] and [[QS:Relevance\|relevance equation]] wiki sections. </div>		<div class='simplebox'> [[File:help.png]] '''Help:''' For more information on relevance equations, check the [[ExpressionScript - Presentation]] and [[QS:Relevance\|relevance equation]] wiki sections. </div>

	=How to copy conditions= <!--T:262-->		=How to copy conditions= <!--T:262-->

C schmitz: Text replacement - "Expression Manager" to "ExpressionScript"

2020-02-11T13:50:11Z

Text replacement - "Expression Manager" to "ExpressionScript"

← Older revision		Revision as of 15:50, 11 February 2020
Line 21:		Line 21:

	<!--T:238-->		<!--T:238-->
	{{Hint\|Text=The conditions functionalities work like a GUI for [[~~Expression Manager~~\|the expressions and equations that can be applied to questions]], allowing the users to easily increase the complexity of their surveys without getting into expressions and relevance equations. However, [[~~Expression Manager~~\|the ~~Expression Manager~~]] must be studied/known to increase the range of options that is available within LimeSurvey.}}		{{Hint\|Text=The conditions functionalities work like a GUI for [[ExpressionScript\|the expressions and equations that can be applied to questions]], allowing the users to easily increase the complexity of their surveys without getting into expressions and relevance equations. However, [[ExpressionScript\|the ExpressionScript]] must be studied/known to increase the range of options that is available within LimeSurvey.}}


Line 292:		Line 292:

	<!--T:42-->		<!--T:42-->
	* a ''comparison operator''. Choose the ''comparison operator'' you want to apply from the dropdown list (''less than'', ''less than or equal to'', ''equals'', ''not equal to'', ''greater than or equal to'', ''greater than'', ''[[~~Expression Manager~~\|regular expression]]'').		* a ''comparison operator''. Choose the ''comparison operator'' you want to apply from the dropdown list (''less than'', ''less than or equal to'', ''equals'', ''not equal to'', ''greater than or equal to'', ''greater than'', ''[[ExpressionScript\|regular expression]]'').


Line 563:		Line 563:

	<!--T:261-->		<!--T:261-->
	<div class='simplebox'> [[File:help.png]] '''Help:''' For more information on relevance equations, check the [[~~Expression Manager~~]] and [[QS:Relevance\|relevance equation]] wiki sections. </div>		<div class='simplebox'> [[File:help.png]] '''Help:''' For more information on relevance equations, check the [[ExpressionScript]] and [[QS:Relevance\|relevance equation]] wiki sections. </div>

	=How to copy conditions= <!--T:262-->		=How to copy conditions= <!--T:262-->

Cdorin: Marked this version for translation

2018-12-06T13:54:08Z

Marked this version for translation

← Older revision		Revision as of 15:54, 6 December 2018
Line 595:		Line 595:


	=Reset conditions=		=Reset conditions= <!--T:271-->


			<!--T:272-->
	To quickly reset all the survey conditions, click on one survey-related setting, look for '''Tools''' on the top toolbar, and click '''Reset conditions:'''		To quickly reset all the survey conditions, click on one survey-related setting, look for '''Tools''' on the top toolbar, and click '''Reset conditions:'''


			<!--T:273-->
	<center>[[File:Reset_conditions_location.png]]</center>		<center>[[File:Reset_conditions_location.png]]</center>


			<!--T:274-->
	Next, confirm on the next page that you want to proceed and all the conditions will be deleted.		Next, confirm on the next page that you want to proceed and all the conditions will be deleted.

Cdorin at 13:52, 6 December 2018

2018-12-06T13:52:19Z

@@ Line 593: / Line 593: @@
 **Scenario 7: Condition C, Condition D -> '''a new scenario is created where the two conditions are added to it'''
 **Scenario 8: Condition F -> not affected
 =Things to watch out for= <!--T:143-->

Han at 07:19, 20 August 2018

2018-08-20T07:19:59Z

← Older revision		Revision as of 09:19, 20 August 2018
Line 8:		Line 8:

	<!--T:9-->		<!--T:9-->
	LimeSurvey has a very powerful logical branching feature. It can be accessed by clicking on the '''Set conditions''' button - [[File:conditions_icon.png]] - located on each [[Question ~~bar~~ options\|question bar]].		LimeSurvey has a very powerful logical branching feature. It can be accessed by clicking on the '''Set conditions''' button - [[File:conditions_icon.png]] - located on each [[Question toolbar options\|question bar]].

	<!--T:10-->		<!--T:10-->

Han at 07:19, 20 August 2018

2018-08-20T07:19:03Z

← Older revision		Revision as of 09:19, 20 August 2018
Line 142:		Line 142:

	<!--T:193-->		<!--T:193-->
	First, you need to access the [[Question ~~bar~~ options#~~Set conditions~~\|conditions designer]]. To do that, click on the question you wish to apply the condition to:		First, you need to access the [[Question toolbar options#The question toolbar\|conditions designer]]. To do that, click on the question you wish to apply the condition to:

Han: si -> is

2018-08-20T07:09:58Z

si -> is

← Older revision		Revision as of 09:09, 20 August 2018
Line 133:		Line 133:

	<!--T:31-->		<!--T:31-->
	However, it is important to understand that '''LimeSurvey automatically determines which logical operator to apply'''. This means that the use of the '''OR '''or '''AND '''operators is determined '''according to the context''' of the condition. In the above example, there is only one scenario. This means that LimeSurvey makes use of [https://en.wikipedia.org/wiki/Boolean_algebra Boolean algebra], which means that operator '''or''' si "computed" first.		However, it is important to understand that '''LimeSurvey automatically determines which logical operator to apply'''. This means that the use of the '''OR '''or '''AND '''operators is determined '''according to the context''' of the condition. In the above example, there is only one scenario. This means that LimeSurvey makes use of [https://en.wikipedia.org/wiki/Boolean_algebra Boolean algebra], which means that operator '''or''' is "computed" first.

	<!--T:32-->		<!--T:32-->
	We'll talk more about complex conditions [[Setting_conditions#The usage of scenarios - Using ORed conditions between different questions\|later]]. Let's first focus together on the elementary ones.		We'll talk more about complex conditions [[Setting_conditions#The usage of scenarios - Using ORed conditions between different questions\|later]]. Let's first focus together on the elementary ones.


	=The conditions designer= <!--T:34-->		=The conditions designer= <!--T:34-->

Cdorin at 09:41, 6 August 2018

2018-08-06T09:41:30Z

← Older revision		Revision as of 11:41, 6 August 2018
Line 14:		Line 14:
	* what conditions you can find in LimeSurvey		* what conditions you can find in LimeSurvey
	* what you can and can't do with conditions		* what you can and can't do with conditions
	* what steps you need to learn to ~~setup~~ simple or more complex conditions		* what steps you need to learn to set up simple or more complex conditions

	<!--T:11-->		<!--T:11-->
Line 21:		Line 21:

	<!--T:238-->		<!--T:238-->
	{{Hint\|Text=The conditions functionalities ~~works~~ like a GUI for [[Expression Manager\|the expressions and equations that can be applied to questions]], allowing the users to easily increase the complexity of their surveys without getting into expressions and relevance equations. However, [[Expression Manager\|the Expression Manager]] must be studied/known to increase the range of options that is available within LimeSurvey.}}		{{Hint\|Text=The conditions functionalities work like a GUI for [[Expression Manager\|the expressions and equations that can be applied to questions]], allowing the users to easily increase the complexity of their surveys without getting into expressions and relevance equations. However, [[Expression Manager\|the Expression Manager]] must be studied/known to increase the range of options that is available within LimeSurvey.}}


Line 45:		Line 45:

	<!--T:16-->		<!--T:16-->
	This approach is different from the '''Jump Branching Logic''' that is sometimes implemented by other ~~softwares~~. In the '''Jump Branching Logic''', the resulting action of a met condition would be to jump to another question (that is to say hide all questions in between). '''LimeSurvey doesn't implement this Jump Branching Logic''' method. Instead, if you wish to jump a series of questions, you should simply set the same condition on all the questions you do not wish to be displayed. For example, if the jump condition you want to set on Question2 is "Jump to Question5 if the answer to Question1 is 'Yes'", you can simply:		This approach is different from the '''Jump Branching Logic''' that is sometimes implemented by other software. In the '''Jump Branching Logic''', the resulting action of a met condition would be to jump to another question (that is to say hide all questions in between). '''LimeSurvey doesn't implement this Jump Branching Logic''' method. Instead, if you wish to jump a series of questions, you should simply set the same condition on all the questions you do not wish to be displayed. For example, if the jump condition you want to set on Question2 is "Jump to Question5 if the answer to Question1 is 'Yes'", you can simply:
	*set a condition on questions 2, 3 and 4 to only display "if the answer to Question1 was '''NOT''' 'Yes'"		*set a condition on questions 2, 3 and 4 to only display "if the answer to Question1 was '''NOT''' 'Yes'"

	<!--T:17-->		<!--T:17-->
	LimeSurvey makes setting the same condition on multiple questions (and thus implementing '''Jump Branching Logic''') easy by allowing you to "copy" a condition from one question to a series of others. In the above example, you would begin by setting the condition on Question2, then from the same screen you would copy that condition to Question3 and Question4.		LimeSurvey makes setting the same condition on multiple questions (and thus implementing '''Jump Branching Logic''') easy by allowing you to "copy" a condition from one question to a series of others. In the above example, you would begin by setting the condition on Question2, then from the same screen, you would copy that condition to Question3 and Question4.

	<!--T:191-->		<!--T:191-->
Line 112:		Line 112:
	Several comparison operators are supported - from the simple "equals" to the advanced "regular expression":		Several comparison operators are supported - from the simple "equals" to the advanced "regular expression":
	* The basic ones refer to the "equal" and "not equal to" operations		* The basic ones refer to the "equal" and "not equal to" operations
	* The ''greater/less than'' operator family is also available, and is usually ~~useful~~ when using numeric question-entries		* The ''greater/less than'' operator family is also available, and is usually used when using numeric question-entries
	** Please note that comparisons on numeric fields make use of the numeric order. For instance, 2 < 10		** Please note that comparisons on numeric fields make use of the numeric order. For instance, 2 < 10
	** If you're using a question entry whose type is text, the condition could be evaluated as "2" > "10" (string order)!		** If you're using a question entry whose type is text, the condition could be evaluated as "2" > "10" (string order)!
Line 375:		Line 375:

	<!--T:57-->		<!--T:57-->
	When you have several conditions, they are '''ORed''' together if they share the same '''tested value'''. This is the case if the condition applies to several answers of one single question. For example, a condition was applied below to three answers belonging to the same question - if answer to Question 'FavColour' equals 'green' '''OR''' answer to Question 'FavColour' equals 'red' '''OR''' answer to Question 'FavColour' equals 'blue', then Question 'BirthDate' will be displayed to the survey respondent:		When you have several conditions, they are '''ORed''' together if they share the same '''tested value'''. This is the case if the condition applies to several answers belonging to one single question. For example, a condition was applied below to three answers belonging to the same question - if answer to Question 'FavColour' equals 'green' '''OR''' answer to Question 'FavColour' equals 'red' '''OR''' answer to Question 'FavColour' equals 'blue', then Question 'BirthDate' will be displayed to the survey respondent:


Line 584:		Line 584:

	<!--T:266-->		<!--T:266-->
	Please pay attention on how the copy conditions functions ~~works~~ when you wish to copy and apply a set of conditions located under different scenarios to another question which uses the same or different scenario id numbers. To summarise the possible cases you might have, check the following example:		Please pay attention to how the copy conditions functions work when you wish to copy and apply a set of conditions located under different scenarios to another question which uses the same or different scenario id numbers. To summarise the possible cases you might have, check the following example:

	<!--T:267-->		<!--T:267-->
Line 616:		Line 616:

	<!--T:148-->		<!--T:148-->
	Setting the following condition "Show question 'FavColour' if answer to question 'Gender' is 'no answer'" really means "show question 'FavColour' if question 'Gender' was displayed to the survey participant who did not submit answer".		Setting the following condition "Show question 'FavColour' if the answer to the question 'Gender' is 'no answer'" really means "show question 'FavColour' if question 'Gender' was displayed to the survey participant who did not submit answer".


Line 627:		Line 627:

	<!--T:150-->		<!--T:150-->
	If you set conditions on a question that, itself, has conditions, you could end up with your survey behaving in ways you might have ~~not~~ predicted. For example, a typical side-effect is that if you hide all questions in a group with chained conditions, the group header will still be shown unless you correct these conditions as explained below.		If you set conditions on a question that, itself, has conditions, you could end up with your survey behaving in ways you might not have predicted. For example, a typical side-effect is that if you hide all questions in a group with chained conditions, the group header will still be shown unless you correct these conditions as explained below.


Line 639:		Line 639:

	<!--T:153-->		<!--T:153-->
	In the above example, the 'Alcohol' question is displayed if the respondent has previously answered to the 'AAMN' question 'No (N)'. However, the 'AAMN' question might not be displayed at the end if the respondent did not select to the previous question ('Gender') answer 'Male (M)'. In this scenario no 'Alcohol' question will be displayed if 'Male (M)' was chosen previously.		In the above example, the 'Alcohol' question is displayed if the respondent has previously answered to the 'AAMN' question 'No (N)'. However, the 'AAMN' question might not be displayed at the end if the respondent did not select to the previous question ('Gender') answer 'Male (M)'. In this scenario, no 'Alcohol' question will be displayed if 'Male (M)' was chosen previously.

	<!--T:269-->		<!--T:269-->
	To have the 'Alcohol' question displayed, you have to copy the conditions from the earlier question(s) to the one you're editing. To have the 'Alcohol' question displayed, you need to ~~setup~~ the following set of conditions:		To have the 'Alcohol' question displayed, you have to copy the conditions from the earlier question(s) to the one you're editing. To have the 'Alcohol' question displayed, you need to set up the following set of conditions:
	* Show 'AAMN' if answer to 'Gender' is 'Male (M)'		* Show 'AAMN' if the answer to 'Gender' is 'Male (M)'
	* Show 'Alcohol' if answer to 'Gender' is 'Male (M)' '''and''' if answer to 'AAMN' is No (N)'.		* Show 'Alcohol' if answer to 'Gender' is 'Male (M)' '''and''' if answer to 'AAMN' is No (N)'.

Line 655:		Line 655:

	<!--T:159-->		<!--T:159-->
	So if you are designing a complicated survey with large number of conditions, make sure you test the survey for as many different combinations of results as you can think of.		So if you are designing a complicated survey with a large number of conditions, make sure you test the survey for as many different combinations of results as you can think of.

	<!--T:270-->		<!--T:270-->
Line 668:		Line 668:

	<!--T:162-->		<!--T:162-->
	If you create a survey where many questions get skipped because of conditions, the progress bar either jumps over a set of questions or the survey ends at 50%.		If you create a survey where many questions get skipped because of conditions, the progress bar either jumps over a set of questions or the survey ends at 50%.

	<!--T:163-->		<!--T:163-->
	To avoid such behavior, the questions that could be skipped should be arranged between the shown questions. In this way only one or two questions get skipped per answer.		To avoid such behavior, the questions that could be skipped should be arranged between the shown questions. In this way, only one or two questions get skipped per answer.

	<!--T:164-->		<!--T:164-->
Line 677:		Line 677:

	<!--T:165-->		<!--T:165-->
	If you arrange the questions in one group and arrange them like: 2A, 2B, 3A, 3B, and so on, you will get a nearly correct progress bar, while arranging the questions like 2A, 3A, 4A, [...], 2B, 3B, 4B, ... you will get a progress bar from 0 to 50% or from 50% to 100%, depending on the answer to the first question.		If you arrange the questions in one group and arrange them like 2A, 2B, 3A, 3B, and so on, you will get a nearly correct progress bar, while arranging the questions like 2A, 3A, 4A, [...], 2B, 3B, 4B, ... you will get a progress bar from 0 to 50% or from 50% to 100%, depending on the answer to the first question.


Line 691:		Line 691:

	<!--T:169-->		<!--T:169-->
	In the multiple options question type, you can use the "Other" provided in the question type as a valid choice but you cannot set conditions on it. For example: Question No 1 says "Which color do ~~your~~ prefer to use?" Answer checkbox choices are Blue, Black and Other. If the participant chooses Blue, you can set a condition. If the participant chooses Black, you can set a different condition. '''However, if the participant chooses "Other" and types in something in the text box, there is NO way a condition can be set.''' LimeSurvey does not recognize if the participant chose the "Other" condition. This is NOT a bug but a limitation.		In the multiple options question type, you can use the "Other" provided in the question type as a valid choice but you cannot set conditions on it. For example, Question No 1 says "Which color do you prefer to use?" Answer checkbox choices are Blue, Black and Other. If the participant chooses Blue, you can set a condition. If the participant chooses Black, you can set a different condition. '''However, if the participant chooses "Other" and types in something in the text box, there is NO way a condition can be set.''' LimeSurvey does not recognize if the participant chose the "Other" condition. This is NOT a bug but a limitation.

	<!--T:170-->		<!--T:170-->