passed/completed error

Is anyone having trouble with their course status not reporting correctly to the LMS? I publish our courses to the LMS with the results as Passed/Failed. Some of the courses report as failed, while others report as completed. This is confusing for some of our users and I've had calls asking what the difference is, but I'm not really sure what to tell them or how to fix it.

Any ideas?

16 Replies
Peter Anderson

Hey Jill, 

Which LMS are you using? You might want to try 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.

Hope that helps narrow down the issue...

Geert De Rycke

Hi Jill

its LMS dependend. That isthat each LMS system has its own way of being informed if all slides have been viewed.

You might want to look into your LMS documentation to see what it wants asinformation.

Here's how you can change it in whezn you publish your course

Select Reporting and Tracking...

 In the section Report status to LMS as: select the appropriate status

as you can see there are 4 different posibilities.

Either you looked it up in your documentation or you do via trial and error .

The picture hereafter is an excerpt from our LMS documentation, so your's should be similar

Hope you find your solution

Geert

Jill Blaser

Thanks, Geert. I've already done the testing and have figured out that Passed/Failed is what our LMS (OnPoint) prefers. The problem is that some courses record as Passed and some report as Completed. I'm trying to figure out why. I am publishing them all the exact same way (Passed/Failed).

Peter,

I'm new to e-learning and the SCORM Cloud sounds like a dream! One of my biggest problems in trouble shooting is that I don't understand the output of the courses I build/design. So when I have an error somewhere, our LMS (OnPoint, by the way) will say it looks like a problem with Storyline. And then I will send a file over to someone at Articulate and am usually told all looks fine. It's frustrating!! But I'm not blaming anyone. I just don't know where to focus my attention because I can't find out where the trouble lies. Throughout beta testing it was often safe to assume that the issues were with Storyline, but lately I haven't had any troubles at all. Smooth sailing. I just can't figure this one out.

I'll look at the SCORM Cloud and see if I can figure out. There may be more questions to follow... 

Thank you so much for the help though! I love this community.

Jill

Paul Zamora

I too have this unresolved issue using Completed/Incomplete in SumTotal V8 LMS.  No matter if you use the tab drop down Passed or Completed.... it always reports as Passed. I've reported this before but with no resolution. So I had to come up with my own.

I recode the lms.js code to report Completed instead of Passed and changed the same code in another .js file to report out Lower Case letters instead of the hard coded 'UpperCase' because SumTotal requires lowercase c for completed.  However, this is only a partial fix. I am still trying to fix antoher reportign bug in that doing this hard code, the course will report a 0 score even on a course with no Quiz or scoring properties.  I am looking to disable that in the .js scripts as well.

BTW the "Passed" reporting issue happens on all Storyline titles I've created not just one so it appears this is a tool bug not a title corruption, unless its my particular installation.

Paul Zamora

This is a consistent bug wtih STL.  I have had to hand code this error out with every course.  One of the issues is that in the lms.js file is this code:

function normalizeStatus(status) 
{
 switch (status.toUpperCase().charAt(0)) {
 case 'C': return "completed";
 case 'I': return "incomplete";
 case 'N': return "not attempted"; 
 case 'F': return "failed";
 case 'P': return "passed";

Most LMSs require a Lower Case variable to report completed. I reported this bug when STL was first released when I found it with my first STL course.  Subsequent updates have yet to fixt this bug.  There is also some other coding you need to do to get it to report correctly, in at least, the SumTotal Systems LMS.  I prefer not to add it here because I do not want to be giving advice which may or may not adversely affect your system or course.

Just know that this is a bug and hopefully it will be fixed.

Ben Mueller

I heard back from Articulate, and they claim to have not heard of this bug before.  I verified the bug with SCORM Cloud and uploaded my test course to their servers.  It's still possible that there already is a bug report for this issue, but if not, then hopefully this will get them on the case.

Paul Zamora

That's odd, I reported this bug a couple of weeks after Storyline came out of their Beta testing.

I even recieved an email from them about it.  However, not much transpired afterwards.  In any case, it's still an issue and only fixed (for me) at this time by recoding some lines in the Java Script files. 

BTW another bug popped up, even after using new code to fix the Completed term issue, now I keep getting a 0 score even when I don't have any Quiz related or sored related material in the title. My last 3 courses are readers with no quiz and in our LMS (SumTotal) we get a 0 Score on non-scored courses.  We now have to hand / re code some java script lines to fix this too.  (again, I prefer not to list recodes because these fixes are only tested in our environment. Don't want to be repsonsible for adverse affects elsewhere...)

Ben Mueller

Just an update here.  I heard back from Articulate Support, and they said that they were able to replicate the bug, and have passed it along to the QA department.  So if this bug really was filed before, hopefully they'll figure that out and merge them.  If somehow the earlier report was lost, then hopefully this triggers them into fixing the problem.