I have a slide with 3 buttons. The Next navigation is disabled until all 3 buttons are visited. Once I advance to the next slide, if I want to return to the previous slide, it makes me click all three buttons to advance again. In Slide Properties I selected "When revisiting: resume saved state" but it isn't working.
Hey there, Peyton. This trigger will fire every time you start the slide's timeline:
Add conditions to it: IF state of RP button is not equal to visited, OR IF state of PACM button is not equal to visited, OR IF state of transport button is not equal to visited.
That way, the Next button will only become disabled if any of those buttons haven't been visited. Let me know how that works!
Great question, Michael. In theory, the next button should not return to disabled when revisiting the slide. However, this is an issue in Storyline 360 and Storyline 3.
If you add a trigger to disable the next button when the timeline starts and set the slide properties to Resume Saved State, the next button will incorrectly return to disabled when you revisit the slide.
Until we have a fix in place, you'll want to use Crystal's workaround of adding conditions to the trigger.
Thanks for the info Alyssa. I didn't know it was a bug. I had myself convinced that this has always been this way and I could never come up with a good explanation as to why. Now I know!
We've consulted with our product team on the behavior where the Next button returns to disabled when revisiting the first slide, and now I have some answers for you.
After careful review, we determined it to be by design based on the navigation features. For next steps, we recommend the settings outlined here.
We'd love to hear your thoughts around this setup, and do let us know if you need a hand!
6 Replies
Hey there, Peyton. This trigger will fire every time you start the slide's timeline:
Add conditions to it: IF state of RP button is not equal to visited, OR IF state of PACM button is not equal to visited, OR IF state of transport button is not equal to visited.
That way, the Next button will only become disabled if any of those buttons haven't been visited. Let me know how that works!
This worked! Thank you!
The question remains: Why does a "when timeline starts' trigger execute again when revisiting a slide that is set to resume saved state?
Great question, Michael. In theory, the next button should not return to disabled when revisiting the slide. However, this is an issue in Storyline 360 and Storyline 3.
If you add a trigger to disable the next button when the timeline starts and set the slide properties to Resume Saved State, the next button will incorrectly return to disabled when you revisit the slide.
Until we have a fix in place, you'll want to use Crystal's workaround of adding conditions to the trigger.
Thanks for the info Alyssa. I didn't know it was a bug. I had myself convinced that this has always been this way and I could never come up with a good explanation as to why. Now I know!
Hello, Peyton and Michael!
We've consulted with our product team on the behavior where the Next button returns to disabled when revisiting the first slide, and now I have some answers for you.
After careful review, we determined it to be by design based on the navigation features. For next steps, we recommend the settings outlined here.
We'd love to hear your thoughts around this setup, and do let us know if you need a hand!
This discussion is closed. You can start a new discussion or contact Articulate Support.