Is there anyway we can restrict the user navigation so that they can only view current and previous slides? If necessary to set up a trigger, how should that be done?
To clarify your question, do you still want to have a "Jump-to-next" button on the slide, but it is unclickable? Or you just want to remove the default next button?
In studio, if you select player templates, you have the capability to restrict navigation that presents users from clicking through the screens with actually reading them. If they try, you get a message that says you must read all of the information on the screen prior to going to the next screen. I think it is connected to the timeline.
I am trying to prevent people from just clicking through the screens and getting to the Quiz section and doing the quiz without really going through the material.
I fully understand how to do it in Studio. The problem I'm having is trying to get it to do the same in Storyline. I don't see anything that gives me access to the Player Templates in storyline.
Even under the Text Labels, there is no Flow section for "Back only" Navigation. If it doesn't have this capability, I think it is something that should be added in upcoming releases. Also, I may have to start using Studio vs Storyline. I did like the trigger and layer capabilities in Storyline, but I think Studio has more functionalities, even with animation capabilities.
I thought you didn't know how to do that in Studio. Sorry about that.
In Storyline, you need to create your own set of back and next button in order to create triggers. (As far as I know, currently Storyline does not allow you to create triggers for its default navigation buttons.)
Once you create your own navigation buttons, here is an example of how to restrict its navigation functions.
Let me know if you need clarification for anything.
First, in reference to this, Cheng,: (As far as I know, currently Storyline does not allow you to create triggers for its default navigation buttons.)
You CAN definitely create triggers for the navigation buttons. Currently, they cannot be hidden, but they can be disabled until you want them activated. See below for some tutorial links.
Second, re this, Robert: In studio, if you select player templates, you have the capability to restrict navigation that presents users from clicking through the screens with actually reading them. If they try, you get a message that says you must read all of the information on the screen prior to going to the next screen.
Storyline DOES provide navigation restriction via the Player menu, but currently no prompt appears. Many of us have asked Articulate to include that in the next version. It would be great if you'd join us in submitting a request.
This support page has information on restricting navigation via the Player menu, and on disabling the Next button until users have finished interacting with a slide and until users have interacted with hotspots.
8 Replies
Hi Robert,
To clarify your question, do you still want to have a "Jump-to-next" button on the slide, but it is unclickable? Or you just want to remove the default next button?
Cheng
In studio, if you select player templates, you have the capability to restrict navigation that presents users from clicking through the screens with actually reading them. If they try, you get a message that says you must read all of the information on the screen prior to going to the next screen. I think it is connected to the timeline.
I am trying to prevent people from just clicking through the screens and getting to the Quiz section and doing the quiz without really going through the material.
Does storyline have that same capability?
Robert,
So you want to restrict the navigation feature until users finish reading the content on the current slide?
If so, you might find this link helpful.
Storyline is fully capable of doing that as well.
Cheng
I fully understand how to do it in Studio. The problem I'm having is trying to get it to do the same in Storyline. I don't see anything that gives me access to the Player Templates in storyline.
Even under the Text Labels, there is no Flow section for "Back only" Navigation. If it doesn't have this capability, I think it is something that should be added in upcoming releases. Also, I may have to start using Studio vs Storyline. I did like the trigger and layer capabilities in Storyline, but I think Studio has more functionalities, even with animation capabilities.
I thought you didn't know how to do that in Studio. Sorry about that.
In Storyline, you need to create your own set of back and next button in order to create triggers. (As far as I know, currently Storyline does not allow you to create triggers for its default navigation buttons.)
Once you create your own navigation buttons, here is an example of how to restrict its navigation functions.
Let me know if you need clarification for anything.
Cheng
Hi Robert and Cheng,
First, in reference to this, Cheng,: (As far as I know, currently Storyline does not allow you to create triggers for its default navigation buttons.)
You CAN definitely create triggers for the navigation buttons. Currently, they cannot be hidden, but they can be disabled until you want them activated. See below for some tutorial links.
Second, re this, Robert: In studio, if you select player templates, you have the capability to restrict navigation that presents users from clicking through the screens with actually reading them. If they try, you get a message that says you must read all of the information on the screen prior to going to the next screen.
Storyline DOES provide navigation restriction via the Player menu, but currently no prompt appears. Many of us have asked Articulate to include that in the next version. It would be great if you'd join us in submitting a request.
This support page has information on restricting navigation via the Player menu, and on disabling the Next button until users have finished interacting with a slide and until users have interacted with hotspots.
Please shout out with any questions.
Thanks Becky for popping in here to assist
This discussion is closed. You can start a new discussion or contact Articulate Support.