When I retake a quiz made from question banks, in the Flash version, the second and subsequent attempts pull in different questions each time. In the HTML5 version, the quiz questions chosen in the initial draw are the same ones that appear every time I retake the quiz. Has anyone else ran into this issue, and if so, is there a setting I should change or a workaround to fix this?
Does it affect all retake QB pulls in SL1 under HTML5? Or only under certain development conditions or when using particular designs of QBs? If only certain conditions or designs, what are those conditions/designs? And what's the best way to compensate for them?
I ask because we have not been able to replicate this in HTML5 in our testing of modules we developed in-house in SL1, yet some of our partners have encountered it. I'm actually working with the OP on the development of a module that uses QBs and may involve retakes in HTML5, and it's a stumper.
Daniel - we are in the investigative stage of this. We have been able to reproduce this error - if you're saying that you cannot, would you be able to share your course with us and provide us some details as to version, etc? This information would be helpful as well.
You are welcome to share here if you cannot share publicly.
Yes, I am on the latest SL version (SL2 Update 4).
For me the issue is happening on ipad, both Safari and Chrome browsers. Have you by any chance tried the Articulate player? I imagine it is the same problem, but have not tested yet; I might do that, although for this particular project we are not using the AP.
Thanks Leslie, unfortunately we are not using the AP for this project, but nevertheless it is good that the AP does support the randomisation of QBs is great!
I have been using the new release 5.1505.515 in the hope that this long standing issue has been resolved (i.e. no randomization using HTML5). but it appears that the bug still exists.
Please could Articulate Staff respond and let me know if indeed the bug still persists and, if so, when will it be fixed? This is a critical issue for my LMS.
OK, many thanks for your prompt response, Leslie (and yours, Ryan). I have tried again with a file built in the earlier release (4) but re-published in v 5 and the issue is still there. Perhaps I have to build a file from scratch in v5? I'd be interested to know if this is how you got the file to work, Ryan (since, according to Leslie, the bug is still there!).
Hey, Ryan -- I just wanted to pop in and let you know that when you reply via email, your signature information is displayed publicly here in the thread, so you are welcome to edit to remove that information if you wish.
This issue is still in the hands of our QA Team and I do not have an update to provide at this time. This thread is attached for our team for both user awareness and to provide and update when applicable.
27 Replies
Hi Pete! This is an issue that our QA Team is aware of. I will add this thread for reference and post an update when applicable.
Awesome, thanks much!
Wondering if there has been any movement or fixes for this coming soon. In lieu of that, Leslie, what are the best workarounds?
Hi Daniel! I popped in to check on this and it is still in the hands of our QA Team, so I have no update to provide at this time.
This thread is flagged so that we can update when applicable.
I would suggest a different approach as there is not a known workaround.
Looking forward to a solution on this at some point :]
Thank you Articulate Team!!
Yes, Ryan. This thread will be updated when applicable, glad you're subscribed now :)
Can I get feedback to understand this error?
Does it affect all retake QB pulls in SL1 under HTML5? Or only under certain development conditions or when using particular designs of QBs? If only certain conditions or designs, what are those conditions/designs? And what's the best way to compensate for them?
I ask because we have not been able to replicate this in HTML5 in our testing of modules we developed in-house in SL1, yet some of our partners have encountered it. I'm actually working with the OP on the development of a module that uses QBs and may involve retakes in HTML5, and it's a stumper.
Daniel - we are in the investigative stage of this. We have been able to reproduce this error - if you're saying that you cannot, would you be able to share your course with us and provide us some details as to version, etc? This information would be helpful as well.
You are welcome to share here if you cannot share publicly.
Leslie, I uploaded a working copy via your file uploader at around 9:30 a.m. EST, Dec. 8. Thank you. I hope this helps.
Thank you! Taking a look now :)
This post was removed by the author
Hi there, I thought I would chime in here and say that the issue persists with SL2.
Any updates?
Thanks, Veronica
I'm patiently waiting for this fix for random Question bank exported to
html5. Have you tried the latest SL build??
Hi Ryan,
Yes, I am on the latest SL version (SL2 Update 4).
For me the issue is happening on ipad, both Safari and Chrome browsers. Have you by any chance tried the Articulate player? I imagine it is the same problem, but have not tested yet; I might do that, although for this particular project we are not using the AP.
Hope the fix comes soon :)
Veronica
Hi Veronica!
You may find that the same questions are shown when retaking a quiz if the following conditions are true:
This is a known issue. You can work around this behavior in either of the following ways:
Thanks Leslie, unfortunately we are not using the AP for this project, but nevertheless it is good that the AP does support the randomisation of QBs is great!
Glad to help!
Hi,
I have been using the new release 5.1505.515 in the hope that this long standing issue has been resolved (i.e. no randomization using HTML5). but it appears that the bug still exists.
Please could Articulate Staff respond and let me know if indeed the bug still persists and, if so, when will it be fixed? This is a critical issue for my LMS.
Many thanks!
Hi Alastair! I can confirm that this issue is still in the hands of our QA Team and I do not have an update to provide at this time.
It works perfectly in the latest SL2 release for html5, just try a test and publish
OK, many thanks for your prompt response, Leslie (and yours, Ryan). I have tried again with a file built in the earlier release (4) but re-published in v 5 and the issue is still there. Perhaps I have to build a file from scratch in v5? I'd be interested to know if this is how you got the file to work, Ryan (since, according to Leslie, the bug is still there!).
Hey, Ryan -- I just wanted to pop in and let you know that when you reply via email, your signature information is displayed publicly here in the thread, so you are welcome to edit to remove that information if you wish.
Hi there, checking to see if Articulate staff have come up with a solution/patch for this issue yet? Any update?
Hi Melissa!
This issue is still in the hands of our QA Team and I do not have an update to provide at this time. This thread is attached for our team for both user awareness and to provide and update when applicable.
Melissa, this functionality is working perfectly for me in an HTML5 SL2 Publish.
This discussion is closed. You can start a new discussion or contact Articulate Support.