SCORM 1.2 Tracking (Articulate 2 to Moodle 2.6.2)
Dec 01, 2014
We’ve been using Articulate and Moodle (LMS) for the pass year. Since upgrading to version 2 we seem to have a problem with the tracking. When publishing in Articulate, we publish with the criteria of a learner only having to complete a certain number of screens to be seen as completed e.g. 22 out of 44. The status to send to the LMS is set to “Complete / Incomplete”. This is the setting we have been using for the pass year. We then set the LMS to look for the same status in the Scorm content and subsequently mark the learner as completed. It seems that although marking “Complete / Incomplete” in Articulate it reports the status to the LMS as “Passed/ Failed”. Only when setting the LMS to “Passed / Failed” it picks up the completed results.
7 Replies
Hello Leon and welcome to Heroes!
This is a known issue with using SCORM 1.2, and is currently being corrected by our QA team. Once an update is available, I will share the information here.
Hi Emily
Thank you for your reply. It's good to know that your team is working on
the solution.
Do you have a time frame of when you expect this to be resolved. We are
using Articulate for a major project launching mid December.
We have been using Articulate 1 for our pilot and not since upgrading,
experiencing this issue.
Thanks
*Leon van Romburgh*
Unfortunately I do not have a timeframe to share. I will post back here with any updates.
Hi
Thank you. The problem we sit with is that we now can't track the progress using Articulate 2. What will you advise, we rather roll back to version 1? Unfortunately our support will then end next year February.
If you must estimate, do you think the bug will be fixed by then?
Thanks
Leon
Sent from Samsung Mobile
Leon,
Honestly I do not know what the timeframe could be. If using Storyline 1 again would be a workaround for this, you could go that route. I will post here as I get any updates.
There is another thread regarding this issue where someone has a workaround. You can take a look here.
Thanks Emily
The workaround seems to be working. We will use this as an interim solutions whilst the "bug" is being fixed.
Leon
Glad to hear the workaround will work for you.
This discussion is closed. You can start a new discussion or contact Articulate Support.