Forum Discussion
Text entry quiz slide marking "Acceptable Answers" as incorrect
I have created a large project in Storyline 360 that requires the user to enter a rule number in a quiz slide. I have entered six variations of the acceptable answer, however, the program is marking these acceptable answers as Incorrect. For example, one of the rule number answers would be typed as 16.A.3.d. -- I created the acceptable answers with and without the periods, with and without spaces between the characters. The only incorrect way to answer would be to get the number wrong and it is case sensitive...so an answer of 16.a.3.D. would be wrong. However, when I enter a right answer of 16.a.3.d., it still marks me as wrong. Any suggestions?
Hi, Amie.
Thank you for reaching out! I'm happy to help!
I followed the instructions on your post when creating a Fill-in-the-blank question, and I could get the answer 16.A.3.d marked as correct. Are you also using Fill-in-the-blank or a different type of question?
Would you be able to share your .story file by either uploading it through this post or privately to me? I'm happy to take a deeper look into your project to see what's going on.
Thank you for your willingness to help. Here is my .story file--I widdled it down to just a few slides (the ones that are throwing the incorrect error) since the original file is extremely large and confidential. Notice that the Acceptable Answers have several variations that would be deemed as "acceptable", including 16.A.3.d. (with a period at the end). The system is telling that is an incorrect answer, but it's listed as the first acceptable answer and is actually the truest version they could enter. Thank you for helping me solve this mystery.
Hi, Amie!
Thank you for sharing your .story file!
Your first option (16.A.3.d.) had an extra space at the end in the acceptable answers, which is why the system would mark 16.A.3.d. as incorrect. Once I deleted the space, it worked!
Can you try this in your original file and see if it works for you?
Oh my goodness, isn't that the silliest oversight? I would have never caught that though, so thank you again for taking the time to troubleshoot this for me!
