Have you tested your course in SCORM Cloud? This would help us determine if the issue is Articulate related or if it's on your LMS's side. If you're using AICC content please take a look at the article below for testing information:
Hi! What version of Saba are you using? I've tested Storyline extensively with Saba and have had to make a couple simple mods to make SCORM 1.2 to work in a Saba 5.5 FP1 LMS.
Christine : the problem is not the LMS but when the module is used in blended learning on Saba. When, on Saba the module is used alone, there is no problem at all...
Saba answers this fact : the "cmi.core.exit" is not defined in the content. How can I define it ?
Gerry ; the Saba version is the 6.1 . It seems the course have a final quiz, does it change anything ?
After publishing your SCORM 1.2 course with Storyline, and before you zip up the course for import into Saba, try this. Works for Saba 5.5 FP1.
In the published output, go to the LMS folder and edit the SCORMFunctions.js file. Look at the second line of text with the SCORM_SUSPEND value.
Change it to this: var SCORM_SUSPEND = "";
Only remove the suspend value and leave the quotes marks alone. Save and exit.
For courses with quizzes, I also edit the imsmanifest.xml file in the main output folder. I look for a line like this for the masteryscore value:
"70" (ignore the quotes)
In the above, 70% is required to pass. I JUST remove the passing score number so I get this:
"" (ignore the quotes)
After those two edits, I then zip up my course for import into Saba.
Doing this last edit insures the content determines completion and not the Saba LMS with the "Is scoring" settings in the Production Repository and Offering entries for the course. I hate "Is scoring" which sends a registration to the transcript as "Unsuccessful" the first time a quiz is completed but not passed. Prefer registration to stay on the enrollments until the learner passes the quiz. Usually don't like it when Saba takes away determining completion from the content.
One last thing, with Storyline Update 3, I find I no longer need to replace the Storyline SCORMFunctions.js file that is described here.
P.S. Saba and SCORM 2004--don't do it, IMVHO. Saba's implementation of SCORM 2004 is too strict and also a little "weird," at least with 5.5.
I am experiencing a different but probably related issue: a Storyline course, published for SCORM 1.2, Passed/Incomplete based on a graded result slide works fine if you go through and pass the course in one sitting. However, anytime you exit the course before it is completed, SABA 5.5 FP1 marks the course Unsuccessful and moves it to Completed Courses.
I wanted to start-up this conversation again as I'm trying to get a course tracking properly for a client using Saba LMS. I've read numerous threads on what hacks others have done to fix issues.
I have a few questions:
1) Just want to confirm that if I have the most recent version of Storyline 2, that I do not need to modify SCORMfunctions.js any longer as noted here ??? (this was resolved in an update?)
2) Client notes that if midway thru a Chapter and click on the Menu tab, you can't resume where you left off. It will start at the beginning of the Chapter. Any idea how to resolve this? I assume this is Saba specific.
3) The course has a quiz. From reading other posts, it sounds like with Saba, whether you pass or fail the quiz, it is treated as a "Completion" status by the Saba LMS. Some have noted to edit the imsmanifest.xml file and delete the "mastery" line. Is this required? Is it possible to publish a Storyline course with a quiz and have it track completion by quiz score and not slides viewed?
4) Anytime you have a course with a quiz, in general should you set LMS Reporting to Passed/Incomplete versus Completed/Incomplete?
Yes, that issue you mentioned was within Storyline 1 - so if you're using Storyline 2, you'll also want to make sure you're on the latest update, which is Update 5 as there was another issue with completion status fixed as a part of update 5 detailed here.
I'll defer to the community in regards to the rest of the specifics of options for the Saba LMS.
Thanks Ashley. I have the latest update, so I assume I don't have to worry about downloading that SCORMfunctions.js file.
As the client wants to track completion based on a quiz result, I'm trying to determine if I need to modify imsmanifest.xml to delete the score value in <adlcp:masteryscore> line, as this was brought up a few times in different posts. I'm curious if most recent Storyline update fixed this issue too.
Hope someone can confirm. Unfortunately I don't have the luxury of doing multiple tests on Saba.
I'm not sure that I've seen that issue with users outside of Saba. Are you able to recreate an issue that you are having in Saba when you test the content in SCORM Cloud?
I can't recreate on my end. Course tracks completion status properly on my LMS. I can publish to SCORM Cloud if that would give me any special info I could use. I'm just sending a Storyline scorm file to the client who uploads and tests in their Saba LMS.
I have set completion status based on quiz result, with "Passed/Complete" setting.
Issue with Saba is that if user fails the quiz, it marks "Results By Module" Completion Status as "Unsuccessful", but marks the "Overall Completion Status" as "Successful". Client wants the Overall Completion status to be Unsuccessful if the quiz is failed.
Hoping someone has some recent experience with publishing to Saba. I can try modifying the imsmanifest.xml file, like Gerry noted above, but that was 2 years ago and I was under the impression by having the latest version of Storyline 2, that this is no longer required when publishing to Saba.
Hi, Hugh -- While I cannot claim to have experience with Saba, I wanted to share these links that cover troubleshooting LMS issues, as hopefully they will prove useful:
Great, Hugh -- glad to help, and would you mind sharing the link to the other post you mentioned here in the thread, so that others who might come across this can access that information, as well? Many thanks! :)
I just compared the SCORMFunctions.js from v4 and v5 of Storyline 2, and they're the same, so I'm guessing/hoping the same fixes will work.
FYI: I'm NOT a Saba or javascript expert. My client told me how to adjust Articulate courses for their Saba LMS. Sorry, but I don't know what version they have. I do know I publish for SCORM 1.2.
16 Replies
Hi Sebastien,
Which patch are you referring to?
Have you tested your course in SCORM Cloud? This would help us determine if the issue is Articulate related or if it's on your LMS's side. If you're using AICC content please take a look at the article below for testing information:
Articulate Support - Testing AICC content at SCORM Cloud
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.
Please let me know how it goes.
Thanks!
Hi! What version of Saba are you using? I've tested Storyline extensively with Saba and have had to make a couple simple mods to make SCORM 1.2 to work in a Saba 5.5 FP1 LMS.
Does your course have a final quiz?
Hello,
Christine : the problem is not the LMS but when the module is used in blended learning on Saba. When, on Saba the module is used alone, there is no problem at all...
Saba answers this fact : the "cmi.core.exit" is not defined in the content. How can I define it ?
Gerry ; the Saba version is the 6.1 . It seems the course have a final quiz, does it change anything ?
Thank you very much
After publishing your SCORM 1.2 course with Storyline, and before you zip up the course for import into Saba, try this. Works for Saba 5.5 FP1.
In the published output, go to the LMS folder and edit the SCORMFunctions.js file. Look at the second line of text with the SCORM_SUSPEND value.
Change it to this: var SCORM_SUSPEND = "";
Only remove the suspend value and leave the quotes marks alone. Save and exit.
For courses with quizzes, I also edit the imsmanifest.xml file in the main output folder. I look for a line like this for the masteryscore value:
"70" (ignore the quotes)
In the above, 70% is required to pass. I JUST remove the passing score number so I get this:
"" (ignore the quotes)
After those two edits, I then zip up my course for import into Saba.
Doing this last edit insures the content determines completion and not the Saba LMS with the "Is scoring" settings in the Production Repository and Offering entries for the course. I hate "Is scoring" which sends a registration to the transcript as "Unsuccessful" the first time a quiz is completed but not passed. Prefer registration to stay on the enrollments until the learner passes the quiz. Usually don't like it when Saba takes away determining completion from the content.
One last thing, with Storyline Update 3, I find I no longer need to replace the Storyline SCORMFunctions.js file that is described here.
P.S. Saba and SCORM 2004--don't do it, IMVHO. Saba's implementation of SCORM 2004 is too strict and also a little "weird," at least with 5.5.
I am experiencing a different but probably related issue: a Storyline course, published for SCORM 1.2, Passed/Incomplete based on a graded result slide works fine if you go through and pass the course in one sitting. However, anytime you exit the course before it is completed, SABA 5.5 FP1 marks the course Unsuccessful and moves it to Completed Courses.
Any ideas?
Hi there,
I wanted to start-up this conversation again as I'm trying to get a course tracking properly for a client using Saba LMS. I've read numerous threads on what hacks others have done to fix issues.
I have a few questions:
1) Just want to confirm that if I have the most recent version of Storyline 2, that I do not need to modify SCORMfunctions.js any longer as noted here ??? (this was resolved in an update?)
2) Client notes that if midway thru a Chapter and click on the Menu tab, you can't resume where you left off. It will start at the beginning of the Chapter. Any idea how to resolve this? I assume this is Saba specific.
3) The course has a quiz. From reading other posts, it sounds like with Saba, whether you pass or fail the quiz, it is treated as a "Completion" status by the Saba LMS. Some have noted to edit the imsmanifest.xml file and delete the "mastery" line. Is this required? Is it possible to publish a Storyline course with a quiz and have it track completion by quiz score and not slides viewed?
4) Anytime you have a course with a quiz, in general should you set LMS Reporting to Passed/Incomplete versus Completed/Incomplete?
Thank you!
Hi Hugh,
Yes, that issue you mentioned was within Storyline 1 - so if you're using Storyline 2, you'll also want to make sure you're on the latest update, which is Update 5 as there was another issue with completion status fixed as a part of update 5 detailed here.
I'll defer to the community in regards to the rest of the specifics of options for the Saba LMS.
Thanks Ashley. I have the latest update, so I assume I don't have to worry about downloading that SCORMfunctions.js file.
As the client wants to track completion based on a quiz result, I'm trying to determine if I need to modify imsmanifest.xml to delete the score value in <adlcp:masteryscore> line, as this was brought up a few times in different posts. I'm curious if most recent Storyline update fixed this issue too.
Hope someone can confirm. Unfortunately I don't have the luxury of doing multiple tests on Saba.
Cheers.
Hi Hugh!
I'm not sure that I've seen that issue with users outside of Saba. Are you able to recreate an issue that you are having in Saba when you test the content in SCORM Cloud?
I can't recreate on my end. Course tracks completion status properly on my LMS. I can publish to SCORM Cloud if that would give me any special info I could use. I'm just sending a Storyline scorm file to the client who uploads and tests in their Saba LMS.
I have set completion status based on quiz result, with "Passed/Complete" setting.
Issue with Saba is that if user fails the quiz, it marks "Results By Module" Completion Status as "Unsuccessful", but marks the "Overall Completion Status" as "Successful". Client wants the Overall Completion status to be Unsuccessful if the quiz is failed.
Hoping someone has some recent experience with publishing to Saba. I can try modifying the imsmanifest.xml file, like Gerry noted above, but that was 2 years ago and I was under the impression by having the latest version of Storyline 2, that this is no longer required when publishing to Saba.
Thanks.
Hi, Hugh -- While I cannot claim to have experience with Saba, I wanted to share these links that cover troubleshooting LMS issues, as hopefully they will prove useful:
How to Troubleshoot Your LMS with SCORM Cloud
Troubleshooting LMS Issues
Thanks Christie. Those are very useful links.
I found another post that provided some settings to change within the Saba LMS, so will see if that fixes the issue.
Great, Hugh -- glad to help, and would you mind sharing the link to the other post you mentioned here in the thread, so that others who might come across this can access that information, as well? Many thanks! :)
I haven't had an SL2-v5 course put into Saba yet, but I was planning to do the same adjustments I've done since SL1, which are described in this post:
https://community.articulate.com/discussions/articulate-storyline/storyline-based-activity-being-marked-unsuccessful-by-saba-lms#
I just compared the SCORMFunctions.js from v4 and v5 of Storyline 2, and they're the same, so I'm guessing/hoping the same fixes will work.
FYI: I'm NOT a Saba or javascript expert. My client told me how to adjust Articulate courses for their Saba LMS. Sorry, but I don't know what version they have. I do know I publish for SCORM 1.2.
I'm having the client test Chris Perez's recommendation of changing Saba's settings as Chris noted in this post here.
Thanks for the info Judy. I'll be trying those adjustments next.
Thanks for your input, Judy! And I appreciate that you followed up with that link also, Hugh. :)
This discussion is closed. You can start a new discussion or contact Articulate Support.