SCORM data model elements in Storyline

May 26, 2020

Is there any information available on what pre-built data model elements are used when publishing SCORM content in Storyline? I'm trying to work out what is produced from publish settings/as standard and what elements are achievable with additional code.


6 Replies
Sam Hill

Hi Kate, I'm not sure if there is information available, but from experience Storyline uses the suspen_data, cmi.objectives and cmi.interactions to store data. It depends on the type of interactions you are building as to whether cmi.interactions are used to store data, but suspend_data is used heavily for data persistence (persistence of variable across session). Are there any in particular you are interested in, or concerned about?

Kate White

Hi Sam, thanks for responding to me. Our LMS provider is developing their SCORM data sets so I've been tasked with finding out what elements are available in Storyline. I have limited knowledge of SCORM development. This is what I have so far....

1st tier data model elements

• cmi.completion_status & cmi.success_status - controlled in publish settings

• cmi.score.scaled (cmi.core.score.raw) - I'm presuming this comes from the results page?

• cmi.session_time (cmi.core.session_time) - I think this is included as standard? 

• cmi.location (cmi.core.lesson_location) - Again I'm pretty sure this is included in order to bookmark the page?

• cmi.exit (cmi.core.exit) - From what you have just told me I understand the default for this is suspend? Can the value of this be changed in the settings?


2nd tier data model elements

• interactions - From what you have said this is built into the pre-built interactions

• objectives - You mention that Storyline uses objectives? Do you know what we can get from this?

• cmi.progress_measure - I've read somewhere that you would need to use a javascript trigger on a slide to use this


entry, mode and credit

• cmi.entry 

• cmi.mode


- I don't know much about these.

Is there anything else that we can get that I've missed? 

Sam Hill

Hi Kate, I'm not sure if it is documented anywhere as to the exact data model elements the published output uses. It would vary based on what your published content included. If the LMS supports SCORM 1.2 RTE-3 then the content will be fully supported. Storyline tends to hide away the SCORM API from the author and does not provide any direct access to the data model. The SCORM tracking is automated, and therefore you won't have a great deal of control over how they are used within content. Articulate have put the emphasis on authoring content and they have made decisions for you regarding the SCORM tracking.

There are things you can change with regards to tracking a completion status and whether you track cmi.interactions (completion of course must be based on quiz results).

My advice would be to build (or source) a test piece of SCORM 1.2 content containing a quiz and running this through the SCORM Cloud service. You can then check the logs to see which data model elements are used. I think the content would give you the information you are looking for.

Admin Account

Hello, I have a similar question to Kate.

I am new to eLearning development and have a client asking if the following SCORM 1.2 considerations would pose a challenge to implementing our course on their LMS system. Is there a way to check for the following in the publishing settings and edit them if needed?

  • The value for cmi.core.score.raw must be set before a value for cmi.core.lesson_status is set. If the lesson status is set before the score and the course has a mastery score, the learner will get sent a "Failed" notification e-mail (even if you send “passed”).
  • Never set a value for cmi.core.exit . Setting any value (suspend, logout, etc) will either
    prevent any data from being saved to the LMS or kick the learner out.
  • The cmi.suspend_data model is limited to 5000 characters. Exceeding this limit will
    drop any existing data and a `null` value will be returned.
  • The cmi.interactions model is not supported in PeopleSoft ELM. This is typically used
    to store data about each interaction, however is not part of the "mandatory"
    specification and break LMS communication if used.
  • The value of cmi.core.session_time must be set using a 4 digit hour
    ( HHHH:MM:SS.MS ). Though the SCORM standard defines "hour" as either 2 or 4 digits,
    using a 2 digit hour will silently break bookmarking and completion.
Katie Riggio

Greetings, Samiah!

It sounds like you're looking for guidance from fellow PeopleSoft ELM users, but I'll try my best to help with relevant resources to your list.

🗒Note: Modifying published output and variables is outside our wheelhouse, so we'll defer this area to our talented community since it may involve custom JavaScript.

If you could share the .story file with us through this private link, we can help you test it in SCORM Cloud as a baseline test with LMS debug mode enabled. This will show us all the data Storyline is sending. 

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