Updating a released course in an LMS, resume behavior after updating a course, tracking suspend data incompatibility

I have an Articulate Storyline 2 course SCORM package in an LMS.  I would love to see a guide as to exactly what will break tracking data for a user and what will not, regarding updating the course in the LMS and a user resuming to where he left off.  

Example 1: I put up a 3-screen course, version A (vA), a user launches and leaves off at screen 2.  I replace vA with vB; all I have done is replace some text on screen 2.  The user launches, gets vB, clicks yes to resume to last screen, resume is successful, the user can continue and attain a status of Complete.

Example 2: I put up a 3-screen course, vA, a user launches and leaves off at screen 2. I replace vA with vB; all I have done is add a new image screen 2. The user launches, gets vB, clicks yes to resume to last screen, resume is successful, the user can continue and attain a status of Complete.

Example 3: I put up a 3-screen course, vA, a user launches and leaves off at screen 2. I replace vA with vB; all I have done is hide the scrolling text box on screen 2. I have not deleted it, I have only hidden the object in the timeline. The user launches, gets vB, clicks yes to resume to last screen, resume fails, the course freezes, the user must launch again and say No and start over.  The suspend data is not compatible.  There are many other surprising examples.

What changes will not make existing suspend data incompatible and what changes will?  

This page: https://www.articulate.com/support/storyline-2/content-wont-resume-after-updating-course-files says if I overwrite existing course files the user will start over in the first slide.   I found this sentiment quoted several times in other forum posts about resuming to an updated course.  That is not at all the case. I have done many, many updates to many courses and thousands of users continue where they left off with no problem.

But there are certain kinds of updates that cause the course to freeze when you resume to updated content or return to a previously visited but updated screen.  Is this documented?

Another example: I put up a 3-screen course, vA, a user launches and leaves off at screen 2.  I replace vA with vB; all I have done is add a new slide between slide 1 and 2.  The user launches, gets vB, clicks yes to resume to last screen, and is taken to the 2nd screen.  The user is not taken to the screen she left off at, she is taken to the new screen in the 2nd slot.  If the user continues, all is well, but if the user clicks PREV when she resumes, it freezes and she has to launch again and start over.

Surely Articulate intended authors to be able to make updates to courses--within reason--without requiring users to start over.  Since I have proven thousands of times that it does not start the user over if you upload new files, what is the actual behavior?  What is within reason--what won't make previous suspend data incompatible with the updated version of the course? What kinds of updates can you do and have the user continue where he left off or revisit updated screens? What kinds of updates can you not do?

Thanks

1 Reply
Ashley Terwilliger

Hi David,

The article you pointed to is what we share in the forums as that is how we would expect it to behave as you're publishing the course again and creating a new copy that is being upload to your LMS. Even if you're overwriting the previous one, it should still be treating it as a new version when it comes to suspend data. 

If you're testing this, has it been LMS specific? Did you also look at testing in SCORM Cloud? If so, and you're finding a difference in our documentation we'd want to investigate that further with the examples you've mentioned and the best course of action for that is to start a Support case.