Going backward....

Hi Ryan,

If you use the "restricted" navigation within the Storyline menu they'll only be able to revisit slides that they've already seen and that would also apply for a revisit to the course as long as you've enabled the "resume". I would set it to always resume vs. giving them the prompt as they could accidentally click "no" and then it's all going to be reset. 

Hi Ashley,

Thanks for the feedback.  I need to make it so the first time they go through it's restricted, but the next time they go through it isn't restricted...

Thoughts?

Should I "resume" it and then make triggers throughout the job aid so that all markers MUST be clicked on to go to the next screen?  If I do that, what if they want to go to a previous screen?  Will the screen be "populated"?

Hi Ryan,

The restricted navigation is defined as:  "This means learners can view the current slide and any slide they previously viewed, but they can't jump ahead or skip over slides." 

It's baked right into the player menu set up, and if it' utilized than the user won't be able to quickly jump from slide to slide using the "next" button either - they'll need to wait for the timeline to be completed. So if they already saw the slides - it would all work as you're describing, that if they were to go back and look at the slides they'd be free. 

If you set the course to resume, they'll be brought back to where they left off previously and could still navigate back to slides that they've seen. If you're looking to have these as entirely separate attempts where they go through it totally restricted the first time, and on a second time come back and start from the beginning that's not something you could accomplish with Storyline's built in navigation. 

Hi Ryan,

First, I wanted to let you know that responding via email includes your email signature here so you may want to edit the post to remove that information.

As for your question - which part are you looking to do with triggers? If it's the second attempt allowing them to navigate freely, you'd still have to have some way to indicate it as the "second attempt" and if they're not resuming it wouldn't be a variable within Storyline that could control it. It may be something you could accomplish with some Javascript elements - but that's beyond my expertise so I'd have to defer to the community.

Hi Ashley,

Thank you so much regarding the comment and my signature.

So within your expertise, the user would have to "redo" the course over again?  Correct?

For clarification: The first time through you want to restrict navigation, so students can only take one path through the material?  Then later you want to open it up so they can explore branches they didn't take the first time, and possibly see new material?

This is an LMS-dependant solution, but If this is what you're trying to do, you could make two modules, one with restricted navigation and one with free navigation.  Then look at your LMS to see if it has a feature to "drip" or "adaptive release" content -- a feature that will release content based on criteria, like dates or scores on previous materials.  Set the first module up so it hides once it's complete, and then release the second module.

I'd be a little leery of doing this with triggers, mainly because I'm worried about how it would affect score reporting.

If the course is restricted then they click around as they have accessed everything in the course.

right?

 If it's restricted then you (and Storyline) are controlling the navigation.  You don't (for example) have a sidebar menu letting users jump to any part of the course.  If you restrict the course, your design could show users all the content as they proceed through the course, or it might hide some content on the first viewing. (I'm working on a course like that now, where the user follows one path in a scenario and gets a grade, but then after it's graded they play the second non-restricted module that lets them explore all the possibilities in the scenario.)

Either way, using an 'adaptive' or 'drip' feature would let you run two slightly different versions of your Storyline file.

Thanks Sharon,

so how would the user go back and forth in a restrictive setting and markers on many screens?

also, see attached.  Why is it that when the trigger is set to keep the "Next" button to be disabled, it won't be "disabled".  Mind=Blown!

Happy to help.  The root of the next button problem is that you're only changing the state when the user clicks a marker.  You haven't changed what happens BEFORE the user clicks the marker, which means Storyline uses its standard Normal state right up until the user clicks.  What you need to do is disable the button as the timeline starts.  You'll see this on the first slide in the attachment below, along with one trigger to enable the button once all states have been visited.  This will cut down on the number of triggers you have to create.

Hi Sharon,

Actually, when I complete the first slide and click next then go back  to that slide, the "Next" button is disabled... This is the problem I'm having... :( hmm

Hi Ryan!

You have the Next button set to Disabled when the timeline starts or Normal when the state changes occur - then you are changing slides, so your settings are not remaining. You need variables for this.

Check out your updated file. This will allow the change to occur on the slide as well as if the user revisits.