Some time ago, i've reported that the retry button does not work in html5 when using questions banks. After the 3rd update i've read that was corrected and it works but the random still not working. In flash works fine but in html5 the random will work onlye the first time, after that stops working and gives the questions in the same order.
What I meant was that this issue does not occur in Articulate SL 360 so that means if you compare the logic, your QA team would know where the issue is with SL2.
I am even wondering if the issue will ever be resolved in SL2 reason being that a new version has already been rolled out. I don't see we will ever be provided with an updated SL2 with this bug fixed.
In this regard if the SL2 will not be updated with fix applied, the only solution I see is to either upgrade to SL 360 or compare the player_complied.js in the mobile folder for both SL2 and SL 360 output that I think holds the logic behind this randomization and directly make modification there to overcome this issue.
Thanks Teg - we'll let them know it's not happening in SL360 too. They are different in terms of the publishing options and code as that was rewritten entirely for the HTML5 only/first options to be included in Articulate 360.
I am using Storyline 2 update 12, and still the Quiz bank randomization seems to be like an issue in HTML5 version. Is this issue resolved ? Works fine in flash version but not in HTML5 and only work for the first time.
Hi Bhupendra. You're right - this is still an issue with Storyline 2. When you retry a quiz, the quiz questions don't randomize in the HTML5 output. As Leslie mentioned, we've added this discussion to our documentation so we can share updates with you here!
Are you experiencing this issue in Storyline 2 as well? I do not have an update to provide, but it is still open with our team and you are in the right place for any updates that we have to share.
34 Replies
Hi Teg,
Can you tell me more about your question regarding published packages and the player?
Hi Alyssa
What I meant was that this issue does not occur in Articulate SL 360 so that means if you compare the logic, your QA team would know where the issue is with SL2.
I am even wondering if the issue will ever be resolved in SL2 reason being that a new version has already been rolled out. I don't see we will ever be provided with an updated SL2 with this bug fixed.
In this regard if the SL2 will not be updated with fix applied, the only solution I see is to either upgrade to SL 360 or compare the player_complied.js in the mobile folder for both SL2 and SL 360 output that I think holds the logic behind this randomization and directly make modification there to overcome this issue.
Thanks Teg - we'll let them know it's not happening in SL360 too. They are different in terms of the publishing options and code as that was rewritten entirely for the HTML5 only/first options to be included in Articulate 360.
Hi
I am using Storyline 2 update 12, and still the Quiz bank randomization seems to be like an issue in HTML5 version. Is this issue resolved ? Works fine in flash version but not in HTML5 and only work for the first time.
Hello Tapas,
This is still an open issue for SL2 specific to question banks and HTML5 output.
I will add this thread as we track user impact and so that we can provide an update if available.
Please note that the only workarounds we are aware of are:
Hi
I am using Storyline 2 update 13, and still the Quiz bank randomization seems to be like an issue in HTML5 version.
Hi Bhupendra. You're right - this is still an issue with Storyline 2. When you retry a quiz, the quiz questions don't randomize in the HTML5 output. As Leslie mentioned, we've added this discussion to our documentation so we can share updates with you here!
Hi
Has there been any progress on this issue?
Thanks
Hello Alex and welcome to E-Learning Heroes :)
Are you experiencing this issue in Storyline 2 as well? I do not have an update to provide, but it is still open with our team and you are in the right place for any updates that we have to share.
This discussion is closed. You can start a new discussion or contact Articulate Support.