LMS override flash cookie is checked. Our LMS is hooked up and there but using the exit button or closing the window never stores a bookmark, looks like it never even attempts to do so through the API js or the functions js.
Have you set up the resume behavior in Storyline as well? What about the slide's revisiting properties? Have you set those to "resume saved state" as well?
Here's the description for each of them - and automatically decide leaves it up to Storyline, which may not always choose what you'd think.
Resume saved state: Use this option if you want the slide to always remember its previous state. In other words, this option lets learners pick up where they left off when they leave the slide and come back to it later. Reset to initial state: Use this option if you want the slide to always reset to its initial state when learners return to it. It'll restart from the beginning of its timeline, and interactive objects will return to their initial states. Automatically decide: This is the default option. It means Storyline will decide whether to resume or reset the slide based on the objects it contains. Here's the logic: If the slide has only simple objects and/or audio but no interactivity, Storyline resets the slide to the beginning of its timeline. However, if the slide contains interactive elements, such as buttons or other objects that have a visited/selected state, Storyline resumes the slide where it left off previously.
so... having a screen with text and a next button will not bookmark anything unless you actually change the resume on that slide? You have do this on every single slide if you want to have an accurate bookmark so when they return it takes them back the screen they were on?
what im trying to get working is, say, course with 10 slides. I start and go to slide 5, hit exit, come back later, and I end up on slide 5.
even switching slides to resume doesn't have the desired effect. Nothing is store or even attempted to be sent to the LMS that would tell the course where to resume from if someone returns.
The bookmarking is dependent on two elements - one, the overall course resume behavior detailed here. Two, the individual slides and their revisiting property - if the user is going to go back to those slides. For the latter, the data is captured as a part of the normal resume, but if the user will be directed back to them for any reason, I'd set the slide to "resume saved state" to save the users position in the slide.
Also, if you're having difficulty with how it's resuming in your LMS you'll also want to test the content at SCORM Cloud which is the industry standard for testing SCORM content to see how it behaves. If the behavior continues at SCORM Cloud, we'll be happy to take a look - otherwise you'll want to connect with your LMS team.
7 Replies
Yes, putting break points on the setBookmarking in API.js or ScormFunctions.js is not being run at all.
Hi Chad,
Have you set up the resume behavior in Storyline as well? What about the slide's revisiting properties? Have you set those to "resume saved state" as well?
so what exactly does "automatically decide" do?
Hi Chad,
Here's the description for each of them - and automatically decide leaves it up to Storyline, which may not always choose what you'd think.
Resume saved state: Use this option if you want the slide to always remember its previous state. In other words, this option lets learners pick up where they left off when they leave the slide and come back to it later.
Reset to initial state: Use this option if you want the slide to always reset to its initial state when learners return to it. It'll restart from the beginning of its timeline, and interactive objects will return to their initial states.
Automatically decide: This is the default option. It means Storyline will decide whether to resume or reset the slide based on the objects it contains. Here's the logic: If the slide has only simple objects and/or audio but no interactivity, Storyline resets the slide to the beginning of its timeline. However, if the slide contains interactive elements, such as buttons or other objects that have a visited/selected state, Storyline resumes the slide where it left off previously.
so... having a screen with text and a next button will not bookmark anything unless you actually change the resume on that slide? You have do this on every single slide if you want to have an accurate bookmark so when they return it takes them back the screen they were on?
what im trying to get working is, say, course with 10 slides. I start and go to slide 5, hit exit, come back later, and I end up on slide 5.
even switching slides to resume doesn't have the desired effect. Nothing is store or even attempted to be sent to the LMS that would tell the course where to resume from if someone returns.
Hi Chad,
The bookmarking is dependent on two elements - one, the overall course resume behavior detailed here. Two, the individual slides and their revisiting property - if the user is going to go back to those slides. For the latter, the data is captured as a part of the normal resume, but if the user will be directed back to them for any reason, I'd set the slide to "resume saved state" to save the users position in the slide.
Also, if you're having difficulty with how it's resuming in your LMS you'll also want to test the content at SCORM Cloud which is the industry standard for testing SCORM content to see how it behaves. If the behavior continues at SCORM Cloud, we'll be happy to take a look - otherwise you'll want to connect with your LMS team.
This discussion is closed. You can start a new discussion or contact Articulate Support.