Restricted navigation Issue Articulate 2

Hi Jeff!

In Articulate Storyline 1, restricted and locked navigation settings only affected the menu. In contrast, the navigation settings in Articulate Storyline 2 affect both the menu and the player buttons, making it much easier to control the overall navigation for your course. To learn how to restrict or lock navigation in Storyline 2, see this article.

I think this is a backward step, we have been given greater control over navigation as it is now possible to restrict the seeker, and disable the next buttons but now have no real control over menu navigation.  From a user perspective in a restrictive menu situation they can click the next button but if the timeline hasn't reached the end there will be no response.  They should at the very least get a warning.  This either means that we have to building a warning or explain the navigation, it is or to the user it will just look responsive. 

Perhaps some users want it to behave like this, I feel this should have been an additional option and restricted navigation should have continued to behave as it always had.

Just my opinion but it has restricted (no pun intended) some of the options I can offer to clients, as the only real workaround is too much work to be economical.

I understand Phil and I have seen that feedback from others, just sharing the explanation :)

I'm sure you know that you can submit those thoughts here as well.

Hi Lesley, I have added in feature request for this when i realised how it had changed, it has just caused me issues recently so thought I would share :-)

Thanks

For anyone wondering if there is a work around in the mean time I just found this thread that has gone on into this issue more extensively, https://community.articulate.com/discussions/articulate-storyline/restricted-navigation?page=5#reply-225852

In short the only work seems to be a custom next button which isn't except-able in my situation.

Thanks Phil!

Thanks for sharing Jeff! I actually meant to link the threads :)

HI Jeff,

I'm not sure if you saw it or not when you looked at the thread I started on this same topic, but I actually have found what I think is a very viable (and actually quite simple) solution to this issue.  Details can be found on page 4 of that thread.  Hopefully this will help you.

Best of luck!

Bobbi

Thanks for posting Bobbi, must have missed that great solution :-)

Thanks for sharing Bobbi i think this will work in the for now. Hopefully they will fix this issue still, I'm always nervous about modifying the scorm packages.