Next Button not appearing

Hi Wendy, quick question .....for future, how do I go about creating a 'custom' state myself? I couldn't seem to find a tutorial on this

Hi Doug!

You can find some information on adding your states here. By naming them and not utilizing a built-in one from the drop down, this makes it 'custom'.

Here are the built-in states.

Thanks!

Hi all,

Thanks for your patience as we investigate the issue associated with the next button not being normal/accessible on a revisit to a slide where you had initially set it to hidden at the start of the slide.  It’s been determined that this behavior is as expected based on what the triggers are telling Storyline, although it may not match what you wanted to occur.

Since the previous/next buttons are set to be hidden at the start of the slide via triggers, when returning to the slide the command given to Storyline is to hide the buttons as soon as the slide starts. The slide is resuming the saved state of the previous/next buttons as expected, but then the triggers tell Storyline to hide them as soon as the slide loads.

This is where applying the conditions to those initial triggers will come into play - as you’ll want to adjust the next/previous buttons to “hidden” only if the user has not visited this slide before. You’ll see this set up in the file I attached that has that trigger/condition set up associated with the state change of the next player button.

Please let us know if you have any other questions!

Ah, happy to hear it Sarah and thanks for the update! 

Can anyone tell me if the new SL3 version has addressed this? In SL1, If the NEXT button was disabled or hidden at the start of the timeline until required interactions were completed, and the slide was set to resume saved state, then when the learner returned to the slide the interactions were still set to completed and the NEXT button was active because that was the state at the end of the slide. But in SL2 that got changed so when a learner returned to the slide, the interactions showed complete but the NEXT button was once again disabled because the timeline restarted. Even though the trigger is Disable NEXT at beginning of timeline IF interactions are False.  Since the interactions are now true, the NEXT button should be active but it's not. I have had to jump through some ridiculous hoops to program variables and states to control the NEXT button outside of tying it to the timeline start to avoid this timeline reset to hidden/disabled.

Hi Tabitha,

The information and example I shared about 9 months ago still holds true, but it sounds like you have applied a condition to the next button similar to my example and that's still not working for you? If so, we'd want to take a look at the .story file in question and I'd ask if you could share it with our Support Engineers using the form here. 

Let me know once you do and I'll follow along! 

This is still an issue for me, I have managed to find a few workarounds, but I just wonder why the "resume saved state" doesn't work. Shouldn't that just recognised where the slide was when the learner left, and then remember if they happen to revisit? 

We need to ensure the learner has read/viewed/heard etc. the content on the slide before continuing. so literally every slide needs to have the next button hidden when they start it and then reveal it at the end for them to continue. But we also need the option for the user to click back through the slides in case they need to revisit something, or they missed something. 

It makes the work twice as much, if not more, to set this up to work, especially when I am trying to create a variance of different slides/experiences to keep the learners engaged e.g click to view more information, click to reveal pictures, click here to watch videos etc. 

"Reset slide works", but then if it is a heavy slide with videos/ interactions etc. it can add a lot of time to the module for the learner, and can also reduce the quality of the experience if they are forced to sit through content unnecessarily again. 

It also means a lot more design time from myself, including testing the module to ensure there are no hiccups with being able to go forward and backwards through the whole slide. Resume Saved State seems to work for everything but the next button.

Sorry if this just seems like i am rambling or complaining, it's just hard when you're looking for an answer and still having the same issue as a 5-year-old thread. 

Hi, Adam, and welcome to E-Learning Heroes! ✨

Thank you for reaching out! 

It sounds like restricting the navigation would work for the scenario you described:

1. Go to the Home tab on the Storyline ribbon and click Player.
2. Click Menu on the player properties ribbon, then click the gear icon at the bottom of the window for additional menu options.
3. Use the Navigation Restrictions drop-down list to choose Restricted.
   • Restricted means learners can view the current slide and any slide they previously viewed, but they can't jump ahead or skip over slides.
4. Mark the box to Restrict Next/Previous buttons. (It's marked by default.)
5. Click OK twice to close the menu options and the player properties.

Let me know if this works!

Hi Adam,

I appreciate you chiming in to share what you are still experiencing with your project file.

I want to take a look at your project file to investigate what's happening with your permission. You can share it publicly here or send it to me privately by uploading it here. I'll delete it when I'm done troubleshooting.