Unusual restriction request
Jan 21, 2019
Hi All!
My client has kind of a strange request involving slide restriction/locking.
They want ALL menu items to be free and unlocked. On each individual slide, they want the next button disabled until the slide has been viewed fully. If the user comes back to a slide a second time, they want the next button unlocked from the beginning.
Now, this is a little strange because if the menu is totally free, there does not seem to be much point in restricting the next button. But this is what the client wants :)
So my question is, is there a way to do this without using a different variable to track the viewed/not viewed status of each and every slide?
I don't think there is, but I thought I would ask the community just in case. Thanks!
John
5 Replies
Hi John,
Could you set the state of the next button to disable till the timeline ends and use the slide property to "resume saved state"? That would bring the learner back to where they left off and allowed the next button to function again without the use of variables.
Let me know if that's oversimplifying the rest of your set up - or if there is a piece we're missing!
It seems like that should work - when I go back to a previous page, the page loads at the end of the timeline as I would expect with "resume saved state"...however the next button is greyed out. Which is very strange because at that point I can't advance at all without using the menu.
The only trigger disabling the next button is at the beginning of the timeline. So I don't see how that could be triggering again when the page loads at the end of the timeline.
Attached here is a sample.
In this file, slide 1.2 will retain the unlocked next button, but slides 1.1 and 1.3 do not.
What's keeping the next button locked on those two slides?
Hi John,
Let's tackle the current setup of your file. I do see that slide 1.2 is the only one working correctly, based on your triggers. After some digging, I found that we have a bug in Storyline where the Next button will incorrectly return to the Disabled state when revisiting a slide.
Fortunately, there's an easy workaround. Instead of using the "change Next button to disabled when timeline starts" trigger, use this:
Check out the change I made in your attached file, and let me know if this workaround is an option for you!
Hello there, John!
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.