We discovered that learner responses from Storyline quizzes were not being communicated to our LMS. I contacted our LMS provider and after some investigation, they determined the SCORM packages are published as 'SCORM 1.3' and need to be published as 'SCORM 2004'. The odd thing is, 'SCORM 1.3' isn't even an option for Storyline 2, and I did publish as 'SCORM 2004'. Any ideas as to what may be causing this inconsistency?
Hi Cassandra! In regards to reporting to the LMS, I agree with Brian and you can test in SCORM Cloud and if you are able to replicate, please share the .story file with us so that we can take a look.
My LMS provider did test on the SCORM cloud and said they received a ‘Parser Warning’. This is what he reported:
I uploaded the package into SCORM cloud and it seems that SCORM cloud is recognizing the package as SCORM 2004 2nd edition. However, when you review the package imsmanifest it seems that the package is publish as a 1.3 object. SCORM cloud is also projecting a "the Sequencing Control Mode 'Flow' was detected on a leaf node, but is only applicable to cluster nodes" parser warning.
Lastly, I did a bit of research on the Articulate forums and it seems that the parser warning is caused by an incorrect value that is produced during the publishing process. This is the link I found: https://community.articulate.com/discussions/articulate-storyline/parser-warning
At this stage since you found errors when testing in SCORM Cloud, I would recommend reaching out to our Support Engineers directly so they can investigate with you to get to the bottom of this as quickly as possible. Be sure to share your case number here with us so we can follow along and relay helpful info in this thread for anyone else in the community that may encounter the same problem! :)
Thanks for sharing your case number here. I see you're working with Victor - you're in good hands! I'll continue to follow along and post updates here as they are available.
7 Replies
I'd suggest testing things via SCORM Cloud to narrow things down to SL or your LMS.
Hi Cassandra! In regards to reporting to the LMS, I agree with Brian and you can test in SCORM Cloud and if you are able to replicate, please share the .story file with us so that we can take a look.
Hi Cassandra! I wanted to point out these directions to help you go through that testing!
Hello all,
Thanks for the replies.
My LMS provider did test on the SCORM cloud and said they received a ‘Parser Warning’. This is what he reported:
I uploaded the package into SCORM cloud and it seems that SCORM cloud is recognizing the package as SCORM 2004 2nd edition. However, when you review the package imsmanifest it seems that the package is publish as a 1.3 object. SCORM cloud is also projecting a "the Sequencing Control Mode 'Flow' was detected on a leaf node, but is only applicable to cluster nodes" parser warning.
Lastly, I did a bit of research on the Articulate forums and it seems that the parser warning is caused by an incorrect value that is produced during the publishing process. This is the link I found: https://community.articulate.com/discussions/articulate-storyline/parser-warning
Any ideas?
Thanks again!
Cassandra
Hi again Cassandra,
At this stage since you found errors when testing in SCORM Cloud, I would recommend reaching out to our Support Engineers directly so they can investigate with you to get to the bottom of this as quickly as possible. Be sure to share your case number here with us so we can follow along and relay helpful info in this thread for anyone else in the community that may encounter the same problem! :)
Hi Alyssa,
Thanks for your help with this. I did submit a case, thanks for the suggestion. My case number is: 00964660
Thanks again!
Cassandra
Thanks for sharing your case number here. I see you're working with Victor - you're in good hands! I'll continue to follow along and post updates here as they are available.
This discussion is closed. You can start a new discussion or contact Articulate Support.