Bookmarking issues

May 08, 2017

Catherine Austin
By Catherine Austin

I am hoping someone can tell me what is going on with this. I have marked for the course to resume where the learner stopped if they get out of the course. I have never had issues with this before, but currently, if someone exits out of my course, they are brought back about 10 slides ahead of where they stopped. If I continue to finish the course where I stopped, it doesn't count the course complete, because I didn't go back and do all of the previous 10 slides that I had previously completed before I exited the course. I am hoping I am making sense here. 

so here it is in outline form - 

1. Finish the course through slide 30, exit the course 40 more slides to go

2. Log back in, It starts on slide 20 instead of 30. 

     if I move forward in the TOC where I was and finish the course - it is marked incomplete

    If I start back at 20 and finish the course it is marked as complete. 

3. Ideally, I would expect the course to start back at 30 and finish the course with a completion. 

Can anyone think of why this is happening?

TIA

 

15 Replies
Ali Goulet
almost 7 years ago05/09/17 at 2:47 pm (UTC)

Hey Catherine,

That's definitely inconvenient and not what I'd expect to happen, sorry you're running into it!

Is this also happening when you test the course in SCORM Cloud? 

If so, would you be able to share your .story project file so I can do some testing? You can attach it here in a comment like this: 

Keep me posted! ☺️

Michael Palko
almost 7 years ago05/15/17 at 4:09 pm (UTC)

I dug a little deeper and am more inclined now to think it's a Saba issue.  When I publish to SCORM Cloud using SCORM 2004 v4, the course behaves as expected, but when doing the same thing in Saba, the course does not resume from the exact spot where I left off.  I thought the resume data limit might be the culprit so that's why I used SCORM 2004.

Ali Goulet
almost 7 years ago05/15/17 at 4:51 pm (UTC)

That's great insight, Michael. Thanks for the update here! In that case, your best bet would be to reach out directly to Saba. 

Feel free to keep us in the loop here on what they find! ☺️

Catherine- Thanks for including those details. Can you share your project file here or privately with our Support Engineers for further investigation? Really appreciate it! 

Kate Taylor
almost 7 years ago06/14/17 at 2:22 pm (UTC)

I am also experiencing this issue.  It is new.  We provide content to the healthcare industry and over the past 120 days have seen an escalation in courses not bookmarking correctly.  These courses have been built in SL2, not 360, and have been viewed on Chrome.  Has anyone tested SL2 against 360 to see if the issue is with SL2?  What about testing in different browsers?  Chrome gives us a lot of trouble with courses built in SL2.  To my knowledge, we haven't identified the cause but I believe publishing in 360 (html5/flash) has resolved some of the cases but not all of them.   Has Articulate responded with a resolution or acknowledgement that this is an issue? 

Alyssa Gomez
almost 7 years ago06/14/17 at 9:47 pm (UTC)

Hi there Kate, so sorry this has been plaguing you! Chrome recently introduced a new security feature that blocks Flash output, and that has had an effect on how some Storyline 2 courses behave when they are launched. This shouldn't have an effect on bookmarking, though. 

I'd like to get some more details from you about the courses that aren't bookmarking correctly. Are you noticing this issue with courses hosted in a learning management system? Have you noticed different behavior in different browsers?

Alyssa Gomez
over 6 years ago09/25/17 at 5:26 pm (UTC)

Hi Jen, sorry you're running into this! I'd be happy to help you narrow this down. Let's start with these details:

  • What version of Storyline are you using?
  • Is the course bookmarking correctly in SCORM Cloud using Edge, Chrome, Firefox?
  • What happens when a learner re-opens the course in the LMS? Does it resume to the incorrect slide?
Michael Palko
over 6 years ago09/26/17 at 2:22 pm (UTC)

Here's a summary of what I've learned from my Saba contact:

The issues you were encountering with your Storyline3 course are most likely a result of the limits on the suspend data field that are set by the SCORM 1.2 specifications.   This is the data that holds information about the numbers of pages viewed, current navigation state, questions answered, etc... during a session and that Saba stores between sessions.

 These requirements according to the specifications are:


Saba adheres to these specifications exactly and they are not currently expandable.  However certain development tools  such as Articulate do not.   Articulate modules of even modest length can easily surpass the 4096 character limit in which case the SCORM 1.2 content will not bookmark or complete correctly in Saba.  Currently, the only remedy in this case is to either break the module into several smaller lessons or to use SCORM 2004 3rd ed. which supports 64,000 characters.   You may also want to try publishing in Tin Can, which functions very much like SCORM 1.2 in Saba. 

I don't want to publish in SCORM 2004v3, so I've taken to creating multiple pieces of smaller content to avoid the issues with the course not resuming exactly where the learner left off.  Not ideal, but workable.

Ashley Terwilliger-Pollard
over 6 years ago09/27/17 at 8:27 pm (UTC)

Hi Michael,

I'm not sure what Saba thinks we're not adhering too? Storyline and Studio are designed to compress all the suspend data to help ensure you don't hit those limits. You can read more about that here. 

The limits are a part of the SCORM Standard and then imposed by each LMS. Some don't enforce the SCORM standards - but that's up to the LMS. 

This discussion is closed. You can start a new discussion or contact Articulate Support.