Storyline 2 SCORM lesson_status

Cheers

I checked with them prior to publishing and it is definitely completed/incomplete.

I will set it up in SCORM Cloud to check, but I do run a Java console that tracks all SCORM settings alongside my local content player.

Hello Tony,

If this does report properly in the SCORM Cloud, you could take a look at this article here about troubleshooting your LMS.

Hi,

just ran the course through SCORM Cloud and get the same reporting on lesson_status as 'passed' not 'completed'

Support case #00437405 has been raised for this issue.

Thanks for the update Tony.

i will keep an eye out on the case as well.

Thanks Emily.

I have had a message back from the support team to say it has been passed to the Quality Assurance team and flagged as critical, but no information as to when or IF(?) it will be addressed.

In some way, I hope it is a content issue and not a packaging problem. It would be a shame if your new product has been released with a fundamental flaw in the SCORM packaging.

At the moment I will have to inform all content developers in our business that they cannot upgrade to SL2 until the problem has been resolved.

TC

Just ran a test and I'm getting the same results as TC for a story that tracks by slides visited. Always sets to passed using this publish setting.

Using a score, I'm getting Completed passed consistently.  The other strangeness is the lesson status is returning as not attempted on subsequent attempts. I would expect this to return the last known status. This could be a SCORM cloud thing.

Looks like the issue is constrained to slide count based completion logic. Another approach to completion is using the Javascript trigger:

var lmsAPI = parent;
lmsAPI.SetScore(90, 100, 0);
SetStatus("completed");

This would enable using a variety of completion conditions beyond those provided out of the box. So if you wanted to say "If the user scores at least 50% on one quiz, 90% on another, and visits slides 15, 25, 35, and 42, they are completed" you could do this with a JavaScript trigger with conditions.

Thanks Steve,

My issue will be that most of the learning designers who are looking to upgrade to SL2 will not have JS skills,

I find it hard to believe that this was not picked up on in the development of the package.

JS is a good skill to develop:) Really opens up what folks can do with stuff developed for browser-based deployment.

I agree ;) I am a Web Developer myself and have fairly strong JS skills.

However I can't force the content developers across our business to learn JS. Most of them are learning designers, who have migrated from the early Studio releases to SL. Triggers can be complicated enough to explain to some, so the idea of trying to take them through JS is daunting to say the least.

One of these days I will try to work out exactly how many people we have within the company who are using Articulate packages.

Heh. I hear you.

I believe the status reported correctly during the beta. Odd things happen during patches and updates. Definitely looks like a problem and I suspect we'll see another point release soon to deal with it.

I was hoping for a speedy response to this problem, but have heard nothing back from the support team other than their apologies.

TC

Hello Tony!

I did check on your case, and it is still being worked on with our QA team. You should receive a response from your email shortly.

Hi,

I had the same issue with SL 1 and it has been fixed in the update 3...

http://fr.articulate.com/support/storyline/lms-shows-passed-instead-of-completed

So I bought SL2 thinking all the previous version's bug have been fixed but obviously sl2 is based on sl1's earlier version's branch...

Today, I'm using the lastest sl1 evaluation version to publish my courses...

Hi Emily,

I have asked for an update from the support team.
Has the response from Phillipe above, been fed back to your developers?

TC

Hello Tony!

I do see that your email was received and you should be hearing back from Regil shortly. I do not see that Phillipe has sent in a support ticket. Hopefully we will have an update for you soon.

Thanks Emily,
Regil has replied to my email saying that there should be a fix in the next update of SL2, but has no information of when that would be released.

TC

Thanks for sharing the information.

Hi,

of course I haven't sent any support ticket. Should I ?

Hello Phillipe!

You would not need to at this point. This issue issue has been addressed by our QA team. I will post here when there is an update available.

Thank you Emily.

Hi there,

I received an email on the 2nd of December saying that this problem was scheduled to be issued with the next update release. Update 3 was then released on the 10th of December with no mention of the issue in the release notes.

Can anyone confirm if it is worth installing this update or will it not resolve the issus I have with the SCORM reporting in SL2?

Regards TC

Hey Tony - 

As I understand it, release 3 was an emergency update that only addressed the single issue. I don't believe any other items were fixed in that release.

Hmm...
Nice to know that, fairly critical, fixes that I was told that have already been resolved were not included.

I have been an advocate of Articulate since very early Studio days and I am really losing faith in the development of the package.

SL2 being released as a new product after the Learning Heroes community provided all of the bug reporting and update suggestions, was a major slap in the face IMHO, and now an issue that is preventing the use of SL2 SCORM packages on our LMS seems to have been put to one side is not what I would call good customer service.

TC

Hello Tony,

As Steve mentioned, Update 3 was an emergency release due to an issue with Adobe Flash Player. You can read more about that here. Currently the team is working on another update to provide other fixes that were already in the works. It would be beneficial to use the update 3, as Storyline will not work when your Flash Player updates to 16.

When the next update is ready, I will post the information here.