Rise Reporting Issue

Hi Alicia, 

It sounds like when you tested at SCORM Cloud, the attempts were tracked there? That is something each LMS will handle, as the launching of the course and recording of scores occurs in the LMS not the published output files. 

Keep us posted if you hear any more from Saba and if you'd like any other help from Miker you can respond to his email to you about case #01090968. 

Thanks Alicia for your case number. It looks like you were working with Miker before? I'll give him a heads up and see what other information we can get for you to share with Saba! 

Thanks for popping in with an update Alicia - I will add this information to your case.

Hi, Logan.

I don't have personal experience with Halogen, but here's how I'd approach the scenario you're describing:

1. Test your course in SCORM Cloud, an industry-standard tool for testing LMS output.  Does the completion problem also happen in SCORM Cloud, or only in Halogen?  This will help you to isolate whether this is a problem with your content or with your LMS.
2. Enable LMS Debug Mode and share the resulting log with Halogen's support team.  LMS Debug Mode logs all communication between the course and the LMS, so Halogen should be able to tell you quickly why course completion isn't being recorded.

Please let us know if you need anything else, and have a great day!

Hi Logan,

Wow - sorry this saga is continuing with your Halogen team. I'd hope they could figure out how the "broke" the system too. 😕 

I haven't heard of similar issues with Halogen, but the debugging steps Justin shared are set in Rise and should generate the log without Halogen's help (it would be different than their own debugging process). Hopefully that helps and gives some further insight into what's happening! 

Definitely keep us posted - I'm sure we have other Halogen users here in ELH. 

Hi,

We're experiencing a similar issue with content developed in Rise. It apparently doesn't make an LMSFinish call when a course is completed. It seems that the only way to trigger this call is to close the browser tab, which isn't helpful when it's one of several lessons in a given LMS course. When we have sequential navigation turned on in our LMS (Skilljar) it means that the leaner is unable advance to the next lesson without closing the browser tab and returning. That's obviously not what we're going for. Given Rise's limited publishing options is there a way to force this LMSFinish call that passes Completion status, and effectively allows learners to advance in a given course when future lessons are locked down?

Hi Bryan,

Great question - we do send the LMSFinish call on the browser close or exit. Are you hoping to change the behavior to occur at a certain point in the Rise course? I'd love to know more about that and share the idea with our team to look into. 

It also sounds like you're linking the Rise courses inside a larger structure with your LMS? Could you also look to see if the Rise courses could launch in a new window/tab? That way they'd be able to close it and still have the LMS page open and continue on through the rest of your courses. 

Hi there, I am experiencing an issue that was mentioned in this thread by Alicia, almost 4 years ago. The attempts on SABA are not being marked. Every attempt is just seen as 1 attempt.

Has anyone figured out how to get the CMI.exit to read blank?

Hi Yesenia! Yes, we would recommend reaching out to SABA's support team for next steps. Please keep us posted on what you find out!