We were experiencing the annoying issue with a republished edited RISE SCORM which was not allowing people to re-open a course, blank screen.
What we had been doing (incorrectly) was to make a copy of the course in RISE .. then we edit the copy... then published the edited copy.. then uploaded the published edited copy to the our LMS.. It was then that incomplete or complete users could not re-open to resume....
On investigation we opened the imsmanifest.xml of both the original SCORM zip and the republished SCORM zip and could see that it had changed the whole internal "identifier" character set in the imsmanifest.xml file of the republished SCORM zip.. so returning users to LMS may have gotten incorrect data request.
We explored Articulate heros and found out... here is thread
that if we "duplicate" the original course within RISE ... and renamed the "duplicate" copy name to indicate it is a copy of the original to keep it for historical version control...
Then go back to and edit if necessary the "original" RISE course with wording changes etc... we experimented with editing in RISE just content words.. then adding a Quiz.. then removing the Quiz.
Then in RISE publish it (the original edited) again... To note is that inspecting the imsmanifest.xml it only changed the last 8 characters in the internal identifier in the imsmanifest.xml file
then we upload this "edited original" SCORM zip file to our LMS...
the republished edited version of the original opened for the users and kept the course completion data and allowed it to resume where it left off.
So it seems that this issue is created when another version of the original course is republished.. it seems RISE doesn't handle version control well ... if the original version is edited and republished the behaviour seems to work as expected.
Side Note... we also found a hack to edit the und.js file in the zipped folder that allowed us to decode the .js file and edit the html and the content .. then re-encode the .js file and replace the original und.js file .. this worked and did not disrupt the completion data of the users.
