Storyline user response is “undefined” for Russian language

May 26, 2016

I'm using Articulate Storyline 2 to develop a e-learning module for English language. Then I made a duplicate of the same module and translated to Russian language. Both modules are published as SCORM 1.2 compliant. I've uploaded them to to test the user tracking.

For English version the log shows cmi.interactions.0.student_response correctly passed. But for Russian version, the cmi.interactions.0.student_response is sent undefined to the LMS.

I understand that this issue is happening because of some special character not parsed properly by the Storyline framework for Russian language. But I don't see any option in Storyline to fix the issue. Or maybe I'm missing something. Any help would be appreciated!

Also added a snapshot of Scorm Cloud log.

6 Replies
Christie Pollick

Hi, Cibin -- Thanks for reaching out, and sorry to hear of your troubles! I think this query might be better directed to our Support Engineers for additional technical insights, so I will go ahead and submit a case on your behalf momentarily. I'll be sure to follow along with their progress and will share relevant updates here for others who may benefit! :)

Cibin Philipose

Hi Christie,

Many thanks for submitting ticket on my behalf. :)

I look forward to hear back from you on responses.

Best regards,

*Cibin Philipose*

Project Leader

Mitr Learning and Media Pvt. Ltd.

A - 615, 616, 617, Sagartech Plaza, Sakinaka Junction,

Andheri - E, Mumbai - 400072 | Office: 022 - 40158739

Mobile: +91 – 7276310826

Christie Pollick

Sure thing, Cibin! And your signature info appearing in the post is not a problem on our end, but in the interests of protecting your privacy, we like to be sure to let you know. 

And it looks like our engineer, Miker, has replied in your case via email to request more information, so please reply to his message, and upload the file he requested via the upload link shared when you have a moment. I will continue to monitor the progress being made! :) 

This discussion is closed. You can start a new discussion or contact Articulate Support.