My company is just in the early stages of bringing Success Factors in and I have been tasked with inputting one of our courses in before rolling out to the rest of the company.
It's all been working fine in Test, however when I input the course in Live it does not show as complete when finished.
I have the SCORM 1.2 box ticked in the launch method, I have Record Learning Event when passed ticked in the Edit Content Object and I have the content is available for launch & Record learning event when all content is complete ticked in the Settings so am at a loss as to what else to do.
Sorry you're running into that while testing in Success Factors. Let's see if we can figure out what's happening.
Have you tried uploading your course to SCORM Cloud to see if the same thing happens? That'll give us a good idea of whether it's file related or LMS related.
I'd also be happy to help test if you share your file here with me. You can add it right in a comment like this:
We use SF and did have issues getting courses to complete when we first implemented it. We mainly work in Adobe Captivate so our settings might not be the same, but I found that SF only recognises incomplete (passed/failed) as a completion status and wouldn't recognise incomplete/complete.
It also sometimes won't recognise courses as complete if they don't have a score. To get round this I usually put 1 point in the course on a button users have to click.
Hi. I have been reading on the page several cases about communication between SCORM 1.2 and Succes Factor, and they all agree that it is not marking as "complete". In the company we have the opposite case. More than 6 months ago we were uploading the Articulate Presenter SCORM packages to ORACLE and there were no problems. A couple of weeks ago we bought the Storyline 360 version, the SCORM package is having problems; It should be noted that a couple of months was changed from supplier of the platform to SUCCESS FACTOR. The course marks as "complete" even when the course was suspended by closing the SAP session. When entering the platform again, it does not allow opening the course even when the ST configuration is set to "always ask". We have already tested with SCORM CLOUD the packaging and it is said that it is OK, but in the LMS it does not communicate according to the configuration or conditioner that activates another resource after "completing" the course. We have tested the variants offered by the 1.2 scorm packaging: completed, error, suspended, approved; But none successful. This has become a bit tedious, because each week we upload content to the LMS and we must explain to people that their content can no longer be seen, it is complicated; Fortunately they are informative caps, they do not carry evaluation, but not all the people take to the good the fact of not being able to re-enter the course. In addition, I have set the platform number of attempts for review, however the order is consecutive and if only allows # review the first content without activating the following. I hope someone can guide me.
Hi Ashley, here reporting me with the recommendation you made me about debugging the LMS. To make the change in the configuration.js you have to unzip the folder and we were not able to re-generate a package. What do you recommend me? I appreciate your kind attention.
From the publish successful window use the "Open folder" button to make the changes, and don't close the publish successful window. Then when you are done, save your changes, close the .js file and go back and use the zip button!
Hi Ashley, how are you? With the novelty we perform the "debugging" test. Effectively, before making the zipp we made the adjustment in configuration.js. However, when publishing the course in the LMS appears the debug window, but still does not respect the "resume" condition. Closing the entire course and can not be reopened and does not activate the next consecutive resource. We have tried with states: suspended, error, completed, approved, incomplete and unsuccessful. Each package has been tested in SCORM cloud and does respect the "restart" condition. The LMS and SAP managers say it is a SCORM error. My boss is worried that Articulate Presenter did not have these errors, and now that we have installed and updated the Presenter plugin these issues have been raised.
What other alternative can we apply? Thank you very much for your support. Greetings.
The debug window only allows you to see what information is being passed back and forth - as a way to share info with your team.
If SCORM Cloud allows it to respect the restart condition and behave as expected, that's not a SCORM error. Have you shared those results with your LMS admins?
Are you using Storyline or Presenter to author these courses? Which version and/or update are you using?
If your LMS doesn't respect the SCORM Configurations, I'm at a bit of a loss as for what else to suggest. 😕
Did everything work for you before in Presenter '13? In Articulate 360 we did change parts of our publishing engine based on the new HTML5 components added in. Could that be what's tripping the LMS up?
10 Replies
Hey Becky!
Sorry you're running into that while testing in Success Factors. Let's see if we can figure out what's happening.
Have you tried uploading your course to SCORM Cloud to see if the same thing happens? That'll give us a good idea of whether it's file related or LMS related.
I'd also be happy to help test if you share your file here with me. You can add it right in a comment like this:
Keep me posted!
Hi Becky,
We use SF and did have issues getting courses to complete when we first implemented it. We mainly work in Adobe Captivate so our settings might not be the same, but I found that SF only recognises incomplete (passed/failed) as a completion status and wouldn't recognise incomplete/complete.
It also sometimes won't recognise courses as complete if they don't have a score. To get round this I usually put 1 point in the course on a button users have to click.
Hope this helps,
Louise
Hi. I have been reading on the page several cases about communication between SCORM 1.2 and Succes Factor, and they all agree that it is not marking as "complete". In the company we have the opposite case. More than 6 months ago we were uploading the Articulate Presenter SCORM packages to ORACLE and there were no problems. A couple of weeks ago we bought the Storyline 360 version, the SCORM package is having problems; It should be noted that a couple of months was changed from supplier of the platform to SUCCESS FACTOR. The course marks as "complete" even when the course was suspended by closing the SAP session. When entering the platform again, it does not allow opening the course even when the ST configuration is set to "always ask". We have already tested with SCORM CLOUD the packaging and it is said that it is OK, but in the LMS it does not communicate according to the configuration or conditioner that activates another resource after "completing" the course.
We have tested the variants offered by the 1.2 scorm packaging: completed, error, suspended, approved; But none successful.
This has become a bit tedious, because each week we upload content to the LMS and we must explain to people that their content can no longer be seen, it is complicated; Fortunately they are informative caps, they do not carry evaluation, but not all the people take to the good the fact of not being able to re-enter the course. In addition, I have set the platform number of attempts for review, however the order is consecutive and if only allows # review the first content without activating the following.
I hope someone can guide me.
Hi Caja,
I can see that you’re still struggling with how it's Storyline is reporting to your LMS since you reached out here and in this other discussion.
I’d love to help.
Can you take a look at the questions I asked in the other discussion? We can keep the conversation going over there!
This post was removed by the author
Hi Ashley, here reporting me with the recommendation you made me about debugging the LMS.
To make the change in the configuration.js you have to unzip the folder and we were not able to re-generate a package. What do you recommend me?
I appreciate your kind attention.
Hi Caja,
From the publish successful window use the "Open folder" button to make the changes, and don't close the publish successful window. Then when you are done, save your changes, close the .js file and go back and use the zip button!
Hi Ashley, how are you?
With the novelty we perform the "debugging" test. Effectively, before making the zipp we made the adjustment in configuration.js. However, when publishing the course in the LMS appears the debug window, but still does not respect the "resume" condition. Closing the entire course and can not be reopened and does not activate the next consecutive resource.
We have tried with states: suspended, error, completed, approved, incomplete and unsuccessful. Each package has been tested in SCORM cloud and does respect the "restart" condition.
The LMS and SAP managers say it is a SCORM error. My boss is worried that Articulate Presenter did not have these errors, and now that we have installed and updated the Presenter plugin these issues have been raised.
What other alternative can we apply?
Thank you very much for your support. Greetings.
Hi Caja,
I'm doing well - thanks!
The debug window only allows you to see what information is being passed back and forth - as a way to share info with your team.
If SCORM Cloud allows it to respect the restart condition and behave as expected, that's not a SCORM error. Have you shared those results with your LMS admins?
Are you using Storyline or Presenter to author these courses? Which version and/or update are you using?
Hi Ashley!
Yes, it shared the information with the LMS administrator, however the platform does not respect the SCORM configuration.
The versions are Storyline 360 and the Presenter was automatically updated in instant ST. We have another Articulate Presenter 13 team.
Hi Caja,
If your LMS doesn't respect the SCORM Configurations, I'm at a bit of a loss as for what else to suggest. 😕
Did everything work for you before in Presenter '13? In Articulate 360 we did change parts of our publishing engine based on the new HTML5 components added in. Could that be what's tripping the LMS up?
This discussion is closed. You can start a new discussion or contact Articulate Support.