Module state changes from COMPLETE to NOT COMPLETE

Hello,
I have a question regarding the SCORM module COMPLETE state. Some of my students would like to go back to a COMPLETE module to review the material before they take a quiz.  Here is the problem:  When they re-open the module, my LMS (Litmos) changes the module state from COMPLETE to NOT COMPLETE.  This forces the student to review EVERY SLIDE IN THE MODULE OVER AGAIN.  Needless to say, my students are not happy.
Litmos says that this is an authoring tool issue, not an LMS issue.  They did some testing and found that RapidIntake and OpenSesame both allow a student to re-enter a COMPLETE module without changing the state.
So my question is "How do I configure Articulate Presenter '09 so that the module state remains at COMPLETE upon module re-entry?"
Thank you!
Paul
10 Replies
Christine Hendrickson

Hi Paul. Welcome to E-Learning Heroes!

Would you mind testing your course in SCORM Cloud to help us determine if the issue is Articulate related or if it's on your LMS's side? If it appears in SCORM Cloud as well, we'd be happy to take a closer look at what might be going on. If you can't replicate the issue in SCORM Cloud, it's probably an issue that you'd want to take to your LMS team. The articles here and here may also help clear up common LMS issues.

Thanks,

Christine

Paul DeBeasi

Hi Christine,

Ok. I signed up for SCORM Cloud, uploaded a short SCORM file, played the file.  The state of the module was then = COMPLETE.  I then re-launched the module.  The first thing I noticed is the message i received is "Would you like to resume your presentation where you left off?" YES or NO.  This is different from the message I receive from Litmos.com (my LMS).  In Litmos, I receive a different message:  "This module has been previously completed. Do you want to start over with this module?"

I relaunched the module and tried answering YES and NO. In both cases, I played a portion of the module and then checked the module state. In both cases, the module stated was = COMPLETE (which is what I want!).

So the same SCORM module behaves differently on Litmos than it does on SCORM cloud. So, any ideas on what could be happening here?   If this is an LMS issue, do you have any pointers/advice I can pass along to them?  

Thank you!  Paul

Christine Hendrickson

Hi Paul!

Awesome, that's a good start. Thanks very much for testing that out, it gives us at least an idea of what's happening. It sounds to me like the resume feature/service on the LMS may be the issue. 

I'm not sure if you saw this earlier, but just in case, this post may help resolve the issue. 

I did manage to find another community member that was running into this issue with Litmos, as well. From what I understand, she was able to change the resume settings for her course in Storyline to fix this issue. I'm wondering if the same would work in Presenter, as well. Here's the thread. It's not exactly the same, but there's not a lot of information about issues with Litmos here, so I'm hoping this will end up being a similar and simple fix for your issue, as well. 

If you need to contact the LMS, I would explain to them that you've tested the content in SCORM Cloud and the presentation functioned properly. You could even provide the content and have them test it, if they're willing to do so. 

If all else fails, we'd be happy to take a look at the files and see if there's a way to get it working properly on the LMS. You're welcome to submit the files in a support case, if you'd like. Please include a Presenter Package, you'll be able to attach it on the second page. Also, if you do submit the case, please share the case number with me. I'll be able to share any additional suggestions or solutions here for anyone else that runs into this issue with Litmos.

Thanks again, Paul!

Holly Mazzeo

Hello - Does anyone have recent experience with this issue? For either Rise or Storyline created modules, if a learner wishes to review the content after completing it, their status changes to In progress in Litmos. (They have to Restart.) Is there a publish/export setting that I am not utilizing that is causing this?