Next Button Issue

Hi Alexia,

I'm sorry to hear about the issues you've run into with the next button. If you're able to share a copy of your .story file here we can take a look at the issue and what may be causing it and any other ideas of ways to fix it. 

From the description, it sounds like the trigger to change the state of the NEXT button is set to "Change state of NEXT button when state of ... are Visited"

Try "Change state of NEXT button when timeline (of the slide) starts IF state of ... is visited and state of ... is visited, etc"

Thanks Walt! I actually have tried that without any luck :( 

I have attached the file. I'm having difficulty with the scene 7, Capitalization. I would like slide 7.3 to show the next button after all menu items have been visited. 

Thanks Alexia for sharing your file.

I know many users have mentioned using the "when object is in a state of" isn't an effective trigger and that connects to Walt's suggestion - but there is a known issue right now with our QA team in regards to the next button still being hidden on a revisit to a slide when it should have changed based on element such as the state of other buttons. 

As our team investigates this, one of the suggested workarounds was to, set the next button to be hidden at .25 seconds into the timeline vs. the start of the timeline. 

Hope that helps, and I'll include the thread here to be included in the report with our QA team, and we'll update you once there is any additional information here. 

Thanks for all your help, Ashley!

I tried your suggestion but sadly, it didn't work. :(

I appreciate you sending this to your QA team. I went ahead and built the previous and next buttons on this page outside of the player as a workaround for now.

Thanks Alexia for testing that out and letting us know what did work for you. We'll keep you posted here once there is any additional information to share. 

Alexia,

Your Storyview is the exact replica of a course I have on my desk right now. Here's what I do:

1 Create 5 T/F variables, 1 each for each "leg" of your course. I call them NavVariable 1, NavVariable2, etc. with an initial value of False.

2. On Slide 7.11 (after the learner has viewed the content, not before),BEFORE the "Jump to 7.3 when user clicks NEXT" trigger, put a trigger to adjust NavVariable 1 to True.  Do the same (with different variables) on slides 7.14, 7.16, 7.24, and 7.26

3. Put this new trigger on 7.3, and be sure it is AFTER the trigger to hide NEXT.

Of course, you have to expand the conditions to include all 5 variables.

The state of variables is always stable, and depending on the state of objects is seldom reliable.

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!