Forum Discussion
Rise not reporting to LMS as Complete
Hi,
Wondering if anyone can help me on make a Rise module communicate with the LMS properly. I've create and published a module (no quiz) based on tracking using course completion. This is set to 100% and when a user reaches the end of the module and closes it, the LMS does not recognise it as completed.
I initially thought that it may be because the user needs to scroll to the bottom of the last page in order to complete and so I tried altering the course completion from 100% to 90% to give a bit of flexibility but this didn't make any difference. Is there anything I'm missing? Also previously in storyline modules you had the option to set a reporting status such as Complete/Incomplete but I can't find this anywhere. Is it possible to apply this in Javascript files once published maybe?
Many thanks for any help.
Kevin
Hi Kevin,
It sounds like you're doing everything correctly! From here, I would give your course a test drive in another LMS environment. That'll narrow down whether this is an issue with your LMS or with the Rise course itself. SCORM Cloud is great for this kind of testing since it's industry standard. Let me know if you'd like some help with that!
Also, I wanted to mention that you can only select a different reporting status in Rise if you choose to 'track using quiz result'.
- StuartMarshall-Community Member
Kevin - Try this tweak to your exported files: https://community.articulate.com/discussions/rise/tracking-using-course-completion
- KevinDicksonCommunity Member
Hi, thanks for the help on this, I've tried changing the reporting Status and this hasn't changed how the module behaves unfortunately. I'm currently looking into using SCORM 2004 to see if this makes any difference.
The module functions correctly on SCORM cloud and from contact the LMS provider (Kallidus) they are just saying its a content issue and there is nothing they can do to help.
It's a shame that Rise looks good but does seem to communicate properly to LMS's. Since yesterday I've read many posts appearing over the last 12 months with people having similar problems (yet to be resolved).
- StuartMarshall-Community Member
SCORM Cloud isn't actually a particularly useful testing system as it can handle absolutely any content - no matter how bad or good it is. Unfortunately most LMSs are not so forgiving.
There are a few other tweaks that can be made in scormdriver.js to see if they help. One for sure worth trying would be to make sure 'exit_suspend_if_completed = FALSE'. There are a few tweaks like this that I have made that have helped with some LMSs that I work with. i can't remember the others offhand but i have a note of them in the office.
- KevinDicksonCommunity Member
Thanks Stuart, I've tried this now also, still no luck. If you do have a chance to send me any other tweaks that would be great.
Hi, Kevin!
Really sorry to hear about the trouble you're having in Kallidus. It's great that the content works in SCORM Cloud, but we want to make sure it works for you too.
A really useful tool for deciphering the communication between your content and your LMS is to enable LMS Debug Mode. This will show you every snippet of communication that your Rise course is sending to your LMS.
If you can provide the resulting LMS Debug Log to Kallidus, they should be able to identify exactly what is missing. Or, you can share the LMS Debug Log with us by clicking here, and we'll help you interpret it.
- KevinDicksonCommunity Member
Thanks Alyssa,
I've run through the module twice, the first time to topic 3 and then I closed it. The second time just to the blank white screen that appears on loading. Any advice you can give on this would be great.
Thanks, Kevin. I'll share these logs with our Support Engineers. They'll take a look and reach out to you via email soon.
- StuartMarshall-Community Member
Hi Kevin. In the scormdriver.js file locate the following function
function SCORM_TranslateExitTypeToSCORM(strExitType) {
WriteToDebug("In SCORM_TranslatgeExitTypeToSCORM strExitType-" + strExitType);
if (strExitType == EXIT_TYPE_SUSPEND) {
WriteToDebug("Returning suspend");
return SCORM_SUSPEND;
} else if (strExitType == EXIT_TYPE_UNLOAD) {
WriteToDebug("Returning Exit");
return SCORM_NORMAL_EXIT;
} else if (strExitType == EXIT_TYPE_FINISH) {
WriteToDebug("Returning Logout");
return SCORM_NORMAL_EXIT;
} else if (strExitType == EXIT_TYPE_TIMEOUT) {
WriteToDebug("Returning Timout");
return SCORM_TIMEOUT;
}
}
and try changing the return value for
EXIT_TYPE_FINISH
fromSCORM_NORMAL_EXIT
toSCORM_LOGOUT
Also, i'd stick with using SCORM 1.2. If you are using 2004 then you'll need to find the equivalent function and replace with
SCORM2004_LOGOUT
- StuartMarshall-Community Member
Alyssa - get them to check out what I have written above as I think this is how it should be. A lot of LMSs allow completion/exit status to be set by lesson status but it should really be set by cmi.exit and to do this properly when a course is completed it needs to send the "logout" message (which isn't getting done by the Articulate scorm driver). I think this is probably responsible for many of the completion issues people are having and it is an issue to do with the content as opposed to the LMS.
Thanks for that information, Stuart. I'll be sure to pass it along to the team.
- StevenvanRoedenCommunity Member
Hi Alyssa, any updates here from your support engineers? I seem to experience the same issues with a Rise course in our LMS