I see the content is sending the score to LMS twice in a minute. you can see the score 7["cmi.core.score.raw = 7"] is passed to LMS even before we reach the result slide without closing the window. Can you please check the LMS communication log text file. I see the first score as question level and the send is overall. These issue is happening only if i failed in the assessment. Can you please check and give solution to this.
Note :- we didn't used customized scorm functionality, we used only default quiz section with result slide.
I took a look at your log file and saw the two scores you were referring to. While there were two scores sent, it looks like the course's status was left unchanged when the score of 7 was sent.
It wasn't until the score of 27 was sent when the status of 'failed' was pushed to the LMS, so there was only one instance of the status changing even though two scores were sent.
With that being said, can I ask what error is being caused by these two scores being sent to your LMS? Are you able to replicate the behavior when you test your course in SCORM Cloud?
If you're able to replicate the behavior in SCORM Cloud, would you be willing to share a copy of your project file here or in private by opening a support case so we can take a closer look at what's happening? We'll delete it when we're done testing!
We have found if you publish a package tracking a results slide (scoring) the manifest includes a mastery score, which causes Saba to ignore the publish settings and turn it into a Pass/Fail package upon adding it to the repository. We routinely use a tool we've built to remove mastery score from the manifest in Storyline zip packages and check Is scoring manually upon addition to the repository. Then the publish settings are retained. We normally publish Pass/Incomplete, but if required by the designer will publish Pass/Fail.
Rise packages do not add the mastery score to the manifest like Storyline does.
2 Replies
Hello Subashini,
Thanks for reaching out!
I took a look at your log file and saw the two scores you were referring to. While there were two scores sent, it looks like the course's status was left unchanged when the score of 7 was sent.
It wasn't until the score of 27 was sent when the status of 'failed' was pushed to the LMS, so there was only one instance of the status changing even though two scores were sent.
With that being said, can I ask what error is being caused by these two scores being sent to your LMS? Are you able to replicate the behavior when you test your course in SCORM Cloud?
If you're able to replicate the behavior in SCORM Cloud, would you be willing to share a copy of your project file here or in private by opening a support case so we can take a closer look at what's happening? We'll delete it when we're done testing!
We have found if you publish a package tracking a results slide (scoring) the manifest includes a mastery score, which causes Saba to ignore the publish settings and turn it into a Pass/Fail package upon adding it to the repository. We routinely use a tool we've built to remove mastery score from the manifest in Storyline zip packages and check Is scoring manually upon addition to the repository. Then the publish settings are retained. We normally publish Pass/Incomplete, but if required by the designer will publish Pass/Fail.
Rise packages do not add the mastery score to the manifest like Storyline does.