I have created a very simple piece of content which has a few pages with some objects: flash movie, iframe - simple stuff like that. Then at the end I have a simple test with 4 questions. And the last page tells the user to click EXIT.

When I publish the content as SCORM 1.2, and then import it into Saba, it works fine. When I launch it it starts automatically; when I finish it passes back results and success/completion statuses correctly.

When I publish the same content as SCORM 2004 it doesn't work. When I launch it in Saba the table of contents is displayed in the navigation frame of Saba's content player, but the content doesn't start automatically - I need to click the module name in the nav frame for the content to actually start. Then when I get to the end no score or statuses are passed back to Saba.

The content is exactly the same - I haven't changed anything; I simply publish it twice - once as 1.2 and once as 2004.

What might be causing the 2004 package to not to work?

Cheers,

Paul Hobbs

Hi Paul,
This is one of those problems with roots in both packages.
Saba is unusual (5.2 sp2 & 5.3 sp1)in that it is 2004 compliant BUT runs the 1.2 and 2004 API's concurrently. So it is up to the contents javascript to check to see which version is present, declare which version it wants to use to Saba and then to tailor it's output to that SCORM version.
This is done so that Saba can run legacy 1.2 content without it breaking, example is the score value passed is totally different between 1.2 (0-100)and '04 (-1 - +1).
You might be best sticking with 1.2 unless your modules are all '04 in which case it ought to be possible to change Saba's default behaviur to 0NLY use the '04 API.