Resetting storyline block
Feb 19, 2018
By
Nicola Fern
Hi
I'm trying to embed a quick calculation-based quiz into my Rise course. It's three questions, and the answers are entered using numeric entry fields.
The interaction works fine the first time round, but if I reset the quiz and return the user to the first screen after they click a 'reset and retry' button, the numeric entry fields are no longer editable.
Any idea why this is happening? The triggers on the button are: Reset results; jump to slide (in that order).
Thanks
Nicola
8 Replies
Hi Nicola! I'm happy to lend a hand. Would you mind sharing the original (unpublished) Storyline file with me? I'll take a peek at your triggers and help you sort this out. 😊
Hi Alyssa, thanks...it's attached!
Hi Nicola!
Thanks for sending your file over to me. I published it to Articulate 360 and added to a Rise Storyline Block here.
Would you mind testing that link and letting me know if the numeric entry fields reset correctly? Keep me posted!
Hi Alyssa, that works fine thanks! What was wrong with it?
Thanks,
Nicola
Hi Nicola!
I actually didn't make any changes to your Storyline file, so I'm thinking you and I may be using different updates of Storyline 360.
Are you on the latest update of Storyline 360? To check, click the Help tab, then click About Storyline. You should see 3.13.14869.0 in the bottom-right corner.
Let me know if you published your Storyline file using the latest version of Storyline 360, and we'll keep digging!
Hi Alyssa
I was using the most up to date version of SL360 – updated again yesterday. I had been initially seeing this problem after editing it in the beta version, but when I saw issues I reverted to using the non-beta. I also was creating fresh files in the non-beta and importing slides from another project, and seeing the same issue.
Nicola
Thanks, Nicola. Let's try this:
Apologies, Alyssa...I had to put this one away for a while.
I've just tried it again with the latest build of SL360 and it works. It doesn't in the beta still so I will report this as a bug.
This discussion is closed. You can start a new discussion or contact Articulate Support.