Resuming with restricted navigation

Hello everybody,

This was done in Storyline 360.

I have a course where the navigation restriction is set to 'restricted'.

I've set the resume option to 'Always resume'

I have published the course, launched it, viewed several pages and closed it.

When I launch the course again, I do resume on the page where I closed the course.

However my problem is the following, when I open the menu it does not let me jump to slides from scenes that I previously visited. Which I would expect to be the behavior when choosing 'restricted'.

I've tested this in our LMS and ScormCloud with the same results.

Does anyone have a solution for this?

 

Thanks in advance,

 

MickyS

30 Replies
Robert Stewart

WISH LIST (menu restricted). Please add an ini file to the root to control menu FREE, RESTRICTED, LOCKED.

I have to get approval before final zip file is created. I have to republish the coarse just to change from FREE (when the approval people jump around to see final changes) and RESTRICTED (when the Gawds above final say zip it).

Life would be better is I only have to change the setting in 1 file on the root e.g. " menu.ini"

Alyssa Gomez

Hello Kshitij and Manjari,

I recently replied to an earlier post from Kshitij here. In that reply, I included a test link for a course with restricted navigation.

If you could both share your project files with us, that would be super helpful! If there is a bug we haven't identified yet, we definitely want to know about it. 

Ren Gomez

Hi Brian,

I just wanted to pop in and let you know that we just released an update for Studio 360 and included a few important fixes that you'll see in the release notes here!
 
The issue you were running into with the interaction slides could be marked unread after resuming a course with restricted navigation has been corrected. Just launch the Articulate 360 desktop app on your computer and click the Update button for Studio 360. Details here.
 
Please let us know if you have any questions, either here or by reaching out to our Support Engineers directly.