SL3 and Restricted menu nav logic from SL2

This thread was a great solution for SL2 courses:
https://community.articulate.com/discussions/articulate-storyline/sl2-restricted-menu-navigation-and-next-button-solution-workaround

However, in SL3 published output there is no "frame.js" file any longer. The solution in the linked post still works for Flash-published content, but not in HTML5 content. The menu remains unrestricted.

Any fix/advice/solution to make this work in SL3 content? Thanks.

6 Replies
Ashley Terwilliger

Hi Richard, 

I haven't seen any other community workarounds on this set up - but it's something that we've got in the pipeline to change this behavior and allow for you to choose some additional navigation options for that. I don't have an ETA on this yet.

I’ll let you know as soon as we have an update on this issue and I’m sorry if it’s slowing you down.

Richard Chasin

Thanks for your response Ashley. I hope the wait is not too long, but we will have to proceed without this functionality.

Setting the menu to Restricted eliminates the ability to custom code the next button functions for HTML5 users, which make up a growing segment of our audience. I hope this gets priority as it impacts out training rather heavily.

Ashley Terwilliger

Hi all,

Great news!  We just released another update for Articulate 360, and included a few important fixes and new features that you'll see in the release notes here.  

The item you may be interested in is how when you restrict or lock navigation, you can now choose whether it impacts just the course menu or also disables the Previous and Next buttons. And you can use triggers to override restricted navigation for individual slides.

Just launch the Articulate 360 desktop app on your computer and click the Update button. Details here.

Please let us know if you have any questions, either here or by reaching out to our Support Engineers directly.