Proposal is that when a scorm lesson is updated, any user who is in progress or complete for that lesson will have the file replay at the beginning without any manual intervention, without the need for a new lesson enrollment.
Maybe a functional suggestion: If the lesson's last updated date is newer than the learner's lesson start date, then play the file from the beginning as it has been deemed as updated.
Currently when a scorm lesson is updated, users who are in progress or have completed that lesson will be met with a gray screen and cannot access that lesson. A user will need to be manually re-enrolled into that lesson resulting in a duplicate enrollment on their reporting. Alternatively they will need to be re-enrolled in the entire course and need to complete all materials again. Absorb's stance in this article is that:
New/Not Started enrollments will be required to take the most up to date version of the content upon launching - not a problem since a user wouldn't have any progress on the lesson. It's a new lesson to them no matter what the content age or version is.
Complete enrollments will not be required to retake content but should see the updated content upon launching. - This is launching into the gray screen state and no updated content is being launched. It's a contridiction of the note below.
In Progress, enrollments may require a reset of the learning object/content being taken as the previous suspend/resume data may not be compatible with the new content. Absorb cannot guarantee interactions between old suspend data and new content.
This can lead to bookmarking incompatibility which may also impact users with complete status and may require a manual reset of the learning objects which can be done at the transcript/edit enrollment page (See example image below).
This presents a problem when trying to maintain simple scorm content where fixing even as much as a typo will result in a complete loss of access to a lesson for any in progress user. While manual lesson updates may work for a handful of users experiencing this, it is not a scalable solution when dealing with thousands of active lesson enrollments.