I have a scenario based training built in SL2 and I included a menu in the player. The course consists of 10 independent mini-branching scenarios. Using the menu, it's possible for a learner to jump straight to the last scenario and complete the training without having completed the first 9 scenarios. Is it possible to track that learners viewed particular slides (i.e. the 10 scenario slides) and only mark completion only when they have? This SCORM is embedded in moodle LMS.
Hi Wendy, we tried the restricted menu and it worked great, except noticed that there was a delay on the "NEXT" button functionality - even though progress to next slide was set to user action/click. So even though we clicked on the next button, it wouldn't progress until some time elapsed and only then it wold allow us to go to the next slide. I found a work around it in the below article, and it seems to work fine now.
Great news Sofia...yes the restricted menu means the user has to wait until the timeline ends before the next button will progress - glad the workaround works for you - good luck with your project!
5 Replies
HI Sofia
do you want them to be able to do the scenarios in any order? or if you want them to do in order you could select a 'restricted menu'
THanks Wendy, I'll try this as it sounds it might work and be a simple solution.
HI Matthew, I signed up for your email ad look forward to finding out how you got around it.
THanks.
Hi Wendy, we tried the restricted menu and it worked great, except noticed that there was a delay on the "NEXT" button functionality - even though progress to next slide was set to user action/click. So even though we clicked on the next button, it wouldn't progress until some time elapsed and only then it wold allow us to go to the next slide. I found a work around it in the below article, and it seems to work fine now.
https://community.articulate.com/discussions/articulate-storyline/sl2-restricted-menu-navigation-and-next-button-solution-workaround
Great news Sofia...yes the restricted menu means the user has to wait until the timeline ends before the next button will progress - glad the workaround works for you - good luck with your project!
This discussion is closed. You can start a new discussion or contact Articulate Support.