Saba 6.1 and Storyline exit before completing the course

Jun 06, 2013

We are upgrading from Saba 5.4.1 to Saba 6.1 and all of our Storyline courses currently contain the JS functionality file needed for the course to mark complete in 5.4.  The issue we are having is not related to completion it is when the user exits the course before the end the course is moving to an unsuccessful status and moves to the completed courses transcript in Saba.  Saba tells us this is the correct functionality.  We do not want the course to be marked unsuccessful until the user has truly completed the course (successfully or unsuccessfully).  Does anyone know of a way to have the .story file stay in it's original status in Saba 6.1 until the user completes the entire course either by passing score or completing a set number of slides?

4 Replies
Dana Collins

Dennis,

I work for a global company and the module in question was created by a colleague in the UK.  The developer is using Storyline Update 1 and I am using Storyline Update 3 (not sure that this matters, but I thought I'd mention it.)  We are publishing for LMS (SCORM 1.2) and we have tried all of the LMS reporting choices (complete/incomplete, passed/incomplete, etc.) and we get the same outcome.  Yes, the issue is happening on a course with 2 or more Storyline files in the same track in Saba 6.1. 

Does this give you enough to go on?

Thanks,

Dana

Dennis Hall

Hi Dana:

Admittedly, I have not touched Saba since last May, however, if I recall correctly, you should set the last course in the curricula with an end marker to get the completion status in Saba.

Look for a related checkbox in the course properties of the last course.

Also, Saba has a built in test facility to test the cmi data. You can find this facility in every course. You simply run it and save the output to a text file. You can then analyze the output to find out why you are getting the incorrect completion results.

There may be a Storyline publish setting (such as marking a course complete after X number of slides viewed) causing this.

I have no access to a Saba system now, so my memory is the best help I can provide.

I hope this helps you.

Best Regards,

Dennis Hall

Michael Grady

Dana and Dennis,

I encountered a similar issue (although with Articulate Studio), and the fix was to place a "transmitting score" at the very end of the course.  We created a .swf file which plays a status bar stretching from left to right, to provide the appearance of something happening in the background.  All it's for is to pause the students from exiting the course too quickly before the data is sent back to the LMS.  (We use this with a global manufacturer)

This discussion is closed. You can start a new discussion or contact Articulate Support.