Exit and LMS Recording

We're doing some testing of Storyline with our LMS (SABA).  A couple of things came up that I can't troubleshoot.  I tried searching, but I can't find the answer.....

1 - When a learner click Exit from the content (we used the exit button on the player), the content player should close, not remain open.  It remains open.  Any solutions?

2 - The data for each attempt at the content (the quiz) must be recorded separately, not rolled up into one attempt.  Is this possible?  

11 Replies
Gerry Wasiluk

Hi, Jenny!

What version of Saba are you using and what Player Template?

I've tested with Saba 5.4 SP2 using the 3.1/5.x Compatibility player template with AICC and SCORM 1.2 content (SCORM 2004 doesn't work well with this version of Saba).

Just had to do this for the SCORM content and the player template I used:  http://www.articulate.com/support/kb_article.php?product=st1&id=guauo7wk0553    -  had to change the exit behavior to "ALWAYS_CLOSE_TOP".

As for #2, at the moment that appears to be an issue.  I've got a SCORM 1.2 course with a final quiz and I take two attempts to pass the course.  Yet when I go to my history, I'm only seeing one launch attempt recorded. 

Also, my module is set to Passed/Incomplete.  When I don't pass the final quiz, Saba acts like a "Failed" instead of an "Incomplete" got sent.

Gerry Wasiluk

Just spent some time doing some more testing.  An AICC module works just fine.  Each launch attempt and the results from trying the final quiz get recorded separately. 

But an equivalent SCORM 1.2 version still acts "weird."   It looks like the right data is being sent (e.g., lesson status of "incomplete" when I don't pass the quiz) but--possibly--Saba is acting weird or doesn't like something in the data being sent to it by Storyline.

Jenny--was your module in AICC or SCORM?

Gerry Wasiluk

Update . . .

Okay I got my "incomplete" issue solved.  It's Saba.  The Storyline content includes a mastery score in the SCORM imsmanifest.xml file.  Anytime Saba gets a mastery score sent to it, Saba wants to determines passing or failing and "ignores" what the content sends (even when you want an "incomplete" for not passing a quiz). 

So when you do not pass the final quiz, Saba fails you on the spot, ignoring the "incomplete" status you want instead and sends the registration to the transcript as "unsuccessful."

So I just edited out the mastery score from the imsmanifest.xml file and my "passed/incomplete" module stayed on my enrollments when I failed the quiz, like it should when an "incomplete" status is sent to Saba.

But, even with that happening, I still see your #2 issue happening.  No explanation yet.  Trying to get access to the db so I can run some SQL queries that would help me look at things more.

Gerry Wasiluk

Okay--I re-read your question and may have misunderstood (but in the process may have uncovered the problem I described above).

When you launch an e-learning course in Saba, that's one "attempt" at the content.  Launch the same course five times with the same registration and that's five attempts at the course.

Each "attempt" can only record one final quiz result, usually the last attempt with the final quiz before exiting.

So, if during one launch session with the content (or, again, one "attempt"), the learner tries the quiz four times before exiting the course, only one set of results with a quiz will get recorded--not four (basically, any previous results get overwritten at the end of a quiz). 

Unless things have changed in newer versions of Saba, Saba does not record each quiz attempt during a single launch session with the content.  Each new try at the quiz has the results updated with the last try at the quiz.

That's the way Saba works and it has nothing to do with Storyline.  It records each launch attempt and only one set of quiz results with each launch attempt (if the final quiz was taken--otherwise you just see the launch attempt).

So if you want to record every learner attempt with the quiz, you must have the learner exit the course after they take the final quiz and then have them re-launch the course to try the quiz again.

Again, assuming newer versions of Saba have not changed, that's just the ways things are with Saba.

(Previous versions of Saba also had a problem recording the final results of a quiz that was tried many times during a single launch session.  Saba tended to just remember the results of the first attempt of the quiz, so having folks always exit after taking a final quiz was often wise.  Don't know if this was ever addressed by Saba.)

****************************************

What I am seeing is this.  I launch a Storyline SCORM 1.2 course five times with the same registration (or five "attempts").  During each attempt, I take the quiz and fail it each time and then exit the course.  Then I re-launch it.

When I look in Saba, it shows me only attempting the course one time with only one set of quiz results recorded.  It should be five attempts with five separate sets of quiz results recorded.

Have never seen that before and it's not right.

If I do the same thing with the same Storyline course, only this time it is published to AICC, each launch attempt (with its quiz results) get properly recorded in Saba.

Inconsistent.  Don't know if its Saba, Storyline, or the two interacting together.  Support case filed on this.

Dave Mozealous

Hi Jenny,

The file you got from Saba might be for our Articulate Studio product, and likely will cause worse issues.  Was the file a SCORMFunctions.js file?

If so, I wouldn't try using that, instead use the attached one.

Here is what you would need to do:

1. Download the attached file

2. Unzip it

3. Replace the SCORMFunctions.js file that is in the published \lms output folder with the attached one

4. Rezip the output and upload to SCORM

Let me know if that resolves the issue for you.  Right now this is just experimental, but would be interested to get your feedback.

-Dave

Jenny Anderson

Dave Mozealous said:

Hi Jenny,

The file you got from Saba might be for our Articulate Studio product, and likely will cause worse issues.  Was the file a SCORMFunctions.js file?

If so, I wouldn't try using that, instead use the attached one.

Here is what you would need to do:

1. Download the attached file

2. Unzip it

3. Replace the SCORMFunctions.js file that is in the published \lms output folder with the attached one

4. Rezip the output and upload to SCORM

Let me know if that resolves the issue for you.  Right now this is just experimental, but would be interested to get your feedback.

-Dave


Dave, it worked!  Each attempt was scored seperately. 

I tried the first recommendation from Gerry regarding the Exit button, it didn't close the window.  There's an alternate fix in the help file, I will test that alternate (my last solution is to just remove the exit button and have them use the close button for the window). 

Thanks for your help!  I think with this progress we're moving forward with a purchase for our department.  YAHOO!

Gerry Wasiluk

Question--is the file Dave M. posted here still experimental?  Newer version?

I've had to use it also for testing SCORM 2004 courses in a client's Saba system.  The client wants to go live with Storyline in the future but needs to know the status of this experimental file first.   And I don't see anything in the Saba KB about this except for SCORM 1.2.  They want to know about SCORM 2004.