Forum Discussion
SCORM 1.2 Suspend Data--Seems Wonky to My Pea Brain
For the last couple of weeks I've been working on a SCORM 1.2 resume issue for a Storyline 2 course that I'm trying to finish up on for a client. I posted on this previously but that post appears n...
Well, hopefully, you can test SCORM 2004 v3 and it can work well, especially as its character limit is 64,000.
For one of my clients, the one using Saba, even though that LMS was supposed to support SCORM 2004 v3, the way Saba implemented SCORM 2004 was so #@#@!#@!#@!#@!# that it was not usable. Got some great help from Articulate, SCORM.COM, and Saba itself but working together we couldn't work around the issue.
Also, back in the days when Articulate 09 first came out we ran into issues when the Saba LMS divided the resume data into multiple database records because the field for the resume data could only hold so many characters.
Every time the suspend data required more than one data record, a Presenter 09 course would act wonky on re-launch for a learner. Among other things, bookmarking never worked.
We never found out what was the problem but we strongly suspected the LMS was doing something with the resume data during initial LMS save or returning it wrong to the Articulate content when it reassembled it into one string on content re-launch. Most often, the quick fix there was to turn off resume for any embedded Engage interactions or Quizmaker quizzes/questions so the resume data could get down to only taking one LMS data record.
Fun problems to debug! :)
