Input data entry question

Hi Ralph,

You should be able to use conditional triggers to get this functionality! (ex. Show layer yes when the variable JaNee changes if variable = yes. else show layer no.) 

Although, since this is a yes/no question having a user input field instead of yes/no buttons does open it up for user error (ex. accidentally adding a space before or after, typing synonyms like sure, typos etc). Do you have a planned response for if the user inputs something other than yes/no?

Hi Catherine,

Thank you for your response. As for your question, the expectation is that the user will answer 'yes' (because this continues the e-learning), but of course it is also possible to answer differently. In that case, I want to lead the user to a 'game over' page with a 'no' or random other answer. To help the user enter the correct answer, I have included an expectation in the text message, namely 'I hope you will say yes'. My idea is that this makes it somewhat clear. I also considered the option of working with 'yes' and 'no' buttons, but I hoped that there would be a solution so that it becomes more of a text message conversation. I'm going to try your tip and let you know ASAP if it worked :-). Thank you very much in advance for your efforts.

Good morning

it is also possible to ask the question again if the answer is different of yes or no. it is necessary to create a variable which corresponds to the answer given and to test whether it corresponds to yes or no or something else. In this third case we ask the question again specifying yes or no as in a normal dialogue.

The biggest issue with things like this is that default Storyline doesnot have a condition to check for 'if string contains'. Thus an answer like JA might be correct, but JA! will fail if not adding conditions for that.

As you can see in this image adding if/then/or conditions in Storyline will rapidly count up.



Solution for that is a simple Javascript trigger that checks whether a variable holds a proper string...but as a beginner that might be tough ;-)

Adding the quick mockup for you...

En uiteraard had dat ook allemaal in het Nederlands gekund ;-)

Hello

I made you a little example.
first slide you enter yes no or other word
second slide I tell you your answer
third slide when you clic on goto we have a look and go to the good slide with trigger.
be careful the order of the triggers is important
I hope I've helped you. Java is therefore not necessarily useful

Although this works...issue is that when you add yes! or y or JA Storyline cannot detect that without extra conditions...and thus you end on the other slide...whereas all 3 could be correct. So you either need to add a lot of conditions...or make sure the user types the exact wording.

If your instructions are clear enough, then you can try this. I used an essay type of slide so I can limit the response length of characters to 3 (to cover the "YES" response). This way I don't have to worry that the learner will type what ever it comes to his/her mind. If the response is anything but "YES" or "NO" (ignore case), the error layer will show for a 2 seconds to visually inform the learner that the response is invalid. If the response is "YES", the "YES" layer will show; the "NO" layer will show if the response is "NO". Check my example below:

https://360.articulate.com/review/content/c2e65a87-5d12-43b4-a027-d929149d8acf/review

I prefer to show a solution that can be done by one's own means rather than going through programming that this person may not understand and having to ask for help again at the next modification, not knowing how it works. . I am for people to have feasible solutions and to be autonomous.

Hi Jean Marc,

Thanks for your comment. That's definitely a good idea to make it seem even more like a conversation. I'm going to consider this in my plan to create a nice escape room. Thanks!

Hi Math,

Wow, thanks for the mock-up. I'm going to take a closer look at this one. Nice to meet a Dutch person too ;-).

What you say is absolutely true and also the struggle to arrange this properly. I also imagine, as a rookie, that this will be a nice first version from which I can definitely learn a lot :-).

Thanks man!

Hi Nedim,

Oh yeah, wow, that's smart too. Limiting the punctuation marks obviously rules out a lot. Smart solution. I'll take a closer look at that too.

Thank you!