Forum Discussion
NEXT button on question slide not working on revisit
I'm having issues with the NEXT button that appears on a question slide when a learner revisits the slide after submitting.
As with your typical question slide, after the learner clicks SUBMIT, if they return to the slide it now has the PREV and NEXT buttons. On this activity slide, the PREV button works fine, but then when the learner wants to move forward again, the NEXT button does nothing; it's not linking to the next slide.
If I manually add the NEXT button in so it appears next to the SUBMIT button, then it works just fine; however, I don't want the NEXT button to appear when they first come to the slide to complete the activity.
All other question slides in the course are working properly; it's just this one that refuses to link to the next slide. Does anyone have any ideas how to fix this?
Hello Dennis! Thanks so much for popping in to share your experience and solution with the community :)
- KendraSutterCommunity Member
i'm not having luck with any of these solutions. the last slide of my quiz would not progress to the last slide in the scene (very next slide). My next attempt is to create a quiz scene and link to that.
- vimalsinghCommunity Member
hi kendra, if possible please share your .story file. so i can take a look on that. and i'm sure it'll be a minor change.
Hey Kendra - Let us know if you need some assistance. You're welcome to share your .story file here for us to take a look.
- ArnieParkCommunity Member
I was able to reproduce this issue and it is a bug with Slide Properties>When revisiting state. When a question slide is revisited (for whatever reason, user nav error etc) and the When Revisiting property is set to Automatically Decide or Resume Saved State, the Prev and Next buttons will appear for some reason and be dead buttons. When I changed the When Revisiting property to Reset to Initial State and revisited the question slide, the submit button does appear.
- vimalsinghCommunity Member
Hi Arnie,
Can you please share a screenshot of the error or probably the .story file so that i can take a look into that?
Hi Arnie,
If you're revisiting a slide that has already been answered, the next/prev buttons should appear by default. This is similar to what you'd see in a quiz question review. Take a look at the additional explanation here.
They should not be "dead" buttons though - unless you're only previewing that one slide. As Vimal suggested, we'd love to take a look at your .story file to test it out. Upload it here using the Add Attachment button at the bottom of the reply window.
- MelissaMaherCommunity Member
I have a question which seems to be related to the issues discussed here. I have six scenes in one Storyline 360 project. The last few slides of each scene are quiz slides. I have each set to Automatically Decide on revisit. The course author doesn't want the settings to Reset to Initial State. Just an FYI, on base layer settings I only have Submit checked. Prev/Next are ok to appear on revisit, though.
When user revisits the last quiz slide in each scene, the next button does nothing. Prev works fine, and both the next/prev buttons in each revisited quiz slide that is NOT the last in the scene work fine.Is this non-functioning NEXT button issue on the last quiz slide in each scene related to the fact that the next slide in the project takes you to another scene?
How can I edit or even see what this revisited last slide NEXT button is set to?Any guidance would be greatly appreciated!
Hey Melissa,
Great question and Nicole explains this beautifully here along with how to solve.
Hope it helps you out as well.
- MelissaMaherCommunity Member
THANK YOU!! I really appreciate your quick and helpful response!
This worked perfectly!
- PeggyHarris-ad9Community Member
This issue hasn't been touched for two years. Yet, here I am, running the most recent v3.37.21614.0, and still running into this problem. I have activated Prev and Submit on a Knowledge Check, which is the last slide of the scene. When the student returns to review this scene, since the question has been answered, the Submit button is now a Next button. That is fine, except that the Next button is "dead" - exactly what Ashley Terwilliger mentioned on 1/18/18, should not be happening. It seems like I should be able to assign an action to the Next button, without performing a confusing workaround.
- LindsayMaiselCommunity Member
OK so I had this exact same problem after all of these years in Storyline 360. My question was the final slide in a scene. I wanted to finish the scene, and jump back into the main menu (another scene/slide). If people revisited the section/question slide, they got stuck in a dead end.
The way I configured this:
Set back, next and submit buttons to be active from the slide properties.
On the question slide base layer, set next to hidden when timeline starts.
Then on each of the final feedback layers (correct, incorrect NOT try again), I set up a few triggers on each layer.
Change the state of submit to hidden when the user clicks "Continue" or whatever your feedback layer button is.
Change the state of next button to normal when the user clicks "Continue" or whatever your feedback layer button is.
MAKE SURE to make these new triggers come BEFORE the trigger for your continue button to advance to the next slide
I also added that next blank slide, set the slide to advance to the menu screen location when timeline starts
Be sure to go into your course menu in the player properties and remove the blank jumping slide from your course menu.
This way, when the user revisits a section or a quiz, the next button is active, they can't change their answer (they had enough tries from the 'Try Again'/attempts settings that were dodged on that question layer feedback). The next pops them out to the redirect to the main menu.Exhausting workaround, but I hope this helps someone else next time!
- RenGomezStaff
Hi Peggy,
Thanks for reaching out, and good call to open a case! It looks like you've discussed this with my teammate, Cleo, who's offered some detailed workarounds that may help you.
I'm sorry we don't have a better design to address this situation, but we have the request Cleo submitted on your behalf on record and will keep tracking this for future improvements.
Once you get some time to try out the workarounds, let Cleo know if you need further help!