Results page not working properly on iPad
Mar 20, 2014
I am having trouble with the the results page of a module on the iPad. This page draws upon five knowledge checks. Learners can see their score and the passing score on this page, and they have the option of returning to retake individual questions through links. This all works perfectly on the laptop. The %Results.ScorePercent% reflects their actual score and it adjusts as expected when they retake questions.
The problem is with the iPad. I cannot get the score above 20% no matter the combination of answers. I have tested both platforms on SCORM cloud and discovered the following:
On a laptop, the cmi.core.score.raw goes up by 20 points every time a question is answered correctly, and the effect is cumulative throughout.
On the iPad, the cmi.core.score raw will also read something like the following: LMSSetValue('cmi.core.score.raw', '20') returned 'true' in 0.002 seconds. But then it resets with the next interaction and ends up as '0' if it is wrong or only '20' again if it is correct.
The only other difference I notice in SCORM Cloud is that on the laptop there are several instances of
Beginning prerequisites evaluation of activity...." after each correct answer. This does not appear when testing on the iPad.
Has anyone else encountered this issue? Any suggestions?
Thanks,
Ryan
5 Replies
Hi Ryan and welcome to Heroes!
I'm sorry to hear about the odd behavior with your results slide. Are you viewing the content within the mobile player or HTML5? It sounds like the latter and I'd like you to to check the individual slide properties and let me know what the revisiting properties are set to?
Hi Ashley. Thanks for the welcome!
Yes, I am viewing the content in HTML5 and not the mobile player. We use Cornerstone as our LMS, and it was while doing a test run with Safari that a member of our team noticed this problem. Since I was able to replicate it on SCORM Cloud, I assumed it must be something internal to Storyline rather than an issue with the LMS.
The revisiting properties on the slides are set to Reset to Initial State. We did this to enable learners to go back and retry the quiz questions.
Hi Ryan,
Thanks for confirming - there is a known issue right now with the "reset to initial state" within the HTML5 output not working as expected, so if you'd like the users to be able to go back and retry their questions you could use the "retry quiz" functionality that is built into the Results slide instead. If you'd like me to confirm that you're experiencing the same issue and then include that within the report filed with our QA team can you share your Storyline file with us? If you'd prefer to share privately please let me know.
Thanks, Ashley.
Unfortunately we can't share the file with you for non-disclosure reasons. I will have to see if we can work around this. How would the retry quiz functionality work when the quiz questions are drawn from knowledge checks throughout the module? Would they just be sent through the five questions successively?
Right now we have the results page organized so that users can revisit jsut those individual knowledge checks that they need to correct. There are also links to several branching scenarios that don't factor into the final score but for which they get individual scores that they may want to improve. It sounds like we would have to take out most of this functionality to get it to work in HTML5.
Hi Ryan,
If you enabled the "retry quiz" setting they'd be brought back to the start of your quiz (you'll see a new trigger appear - jump to X slide) and they'd have the option to redo the questions. Depending on what you've got set up, there is also a method here to set it up to only go to your questions where the user got it wrong. Is this the method your using?
In regards to your other scenarios, if the user is being shown a score on a results slide, you could use the same method - just don't track that results slide within your LMS publishing options if it's only for their personal growth.
This discussion is closed. You can start a new discussion or contact Articulate Support.