My project requires restricted access to ensure learners receive all compliance information. However, I do want the learner to be able to review slides in a previously viewed scene in an unrestricted way.
What do I need to do to make that happen? Do I have to have a visible menu in my Player to make that happen?
In the Player, you can set the Menu to Restricted navigation. That automatically disables the NEXT button until the timeline finishes playing. And it only does that the first time the user visits the slide. Thus, the user can easily revisit any slide without having to wait for its timeline to finish.
That functionality works with or without the Menu showing.
If you do show the Menu (and it is set to Restricted):
The user will be able to return to any previously viewed item by clicking it in the Menu.
The user will not be able to advance to a new slide.
Note: Special triggers to force a user to complete an interaction will override the default Restricted-navigation function. So, for example, suppose a slide contains triggers to disable NEXT if a variable is false, enable NEXT when a set of buttons are all visited, and set the variable to True when the buttons are visited. On that slide, the Restricted-navigation function would not enable the NEXT button when the timeline ends.
@Judy Nollet: Special trigger applies to Next button from player or only custom Advance button ? I tried this in Storyline 360 but is not working with player deault Next button. It gets enabled when timeline ends irrespective of leaner visited the buttons on slide.
Hi Catherine, if the content is being deployed as SCORM to an LMS you will find that once a slide has been visited, it will be unlocked on subsequent visits. You are not likely to see this behaviour work consistently when viewing a web output or on Review 360. I would recommend testing the content on SCORM Cloud, which is a free service (provided the published output is smaller than 100mb) which allows you to test SCORM content. Using SCORM will ensure that the users state is persisted from session to session. As mentioned, this won't be the case for content published for Web and Review 360. I think your content is most likely functioning as intended already.
Thank you, Sam. I thought something was screwy when it was viewed in Review 360. Didn't seem to navigate as expected. Since our LMS isn't live as yet, I can upload and try it there. Thanks for letting me know about SCORM Cloud. I'm assuming that service doesn't retain any rights to the content uploaded into it, right?!
The "Special triggers" I mentioned refer to customtriggers that a developer would add to a given slide. If those triggers are set up correctly, they override the functionality of the built-in Restricted navigation. The built-in Restricted navigation applies only to the built-in Next button in the player. It can't control any custom buttons.
If you want more information, there are multiple forum posts about triggers that force the user to complete an interaction.
8 Replies
Hi Catherine. How is the course being delivered? Are you publishing to SCORM and delivering on an LMS?
That is the ultimate destination -- our LMS via SCORM output.
Catherine,
In the Player, you can set the Menu to Restricted navigation. That automatically disables the NEXT button until the timeline finishes playing. And it only does that the first time the user visits the slide. Thus, the user can easily revisit any slide without having to wait for its timeline to finish.
That functionality works with or without the Menu showing.
If you do show the Menu (and it is set to Restricted):
Note: Special triggers to force a user to complete an interaction will override the default Restricted-navigation function. So, for example, suppose a slide contains triggers to disable NEXT if a variable is false, enable NEXT when a set of buttons are all visited, and set the variable to True when the buttons are visited. On that slide, the Restricted-navigation function would not enable the NEXT button when the timeline ends.
@Judy Nollet: Special trigger applies to Next button from player or only custom Advance button ? I tried this in Storyline 360 but is not working with player deault Next button. It gets enabled when timeline ends irrespective of leaner visited the buttons on slide.
Hi Catherine, if the content is being deployed as SCORM to an LMS you will find that once a slide has been visited, it will be unlocked on subsequent visits. You are not likely to see this behaviour work consistently when viewing a web output or on Review 360. I would recommend testing the content on SCORM Cloud, which is a free service (provided the published output is smaller than 100mb) which allows you to test SCORM content. Using SCORM will ensure that the users state is persisted from session to session. As mentioned, this won't be the case for content published for Web and Review 360. I think your content is most likely functioning as intended already.
Thank you, Sam. I thought something was screwy when it was viewed in Review 360. Didn't seem to navigate as expected. Since our LMS isn't live as yet, I can upload and try it there. Thanks for letting me know about SCORM Cloud. I'm assuming that service doesn't retain any rights to the content uploaded into it, right?!
I'm assuming that service doesn't retain any rights to the content uploaded into it, right?! - That's correct.
Devi,
The "Special triggers" I mentioned refer to custom triggers that a developer would add to a given slide. If those triggers are set up correctly, they override the functionality of the built-in Restricted navigation. The built-in Restricted navigation applies only to the built-in Next button in the player. It can't control any custom buttons.
If you want more information, there are multiple forum posts about triggers that force the user to complete an interaction.
This discussion is closed. You can start a new discussion or contact Articulate Support.