Send xAPI Statement Storyline action doesn't work when used within Rise

Aug 02, 2022

I have a single Storyline 360 slide that has several Send xAPI Statement actions.  When I publish that slide to an LMS in cmi5 format and import it into my LMS (SCORM Cloud for testing), it works perfectly and I can see all the interactions logged, including my Send xAPI Statement actions.

However, if I publish this to Review360 and then embed the exact same slide into a Rise course that is also exported to my LMS using cmi5, none of the interactions with the Storyline slide are logged other than a simple "Experienced" statement on the slide.  None of the interactions with any of the components within the slide are logged.

So, it seems like Storyline behaves differently when used as a block within Rise compared to being used natively within an LMS.  Is this a bug, and is anyone aware of a way I can get Rise to pass on the xAPI actions from Storyline to the LMS?  Thank you.

3 Replies
Jose Tansengco

Hi Ian,

Thanks for reaching out!

It is expected behavior for Storyline 360 blocks that are embedded in a Rise 360 course to not be be able to send data to an LMS. This is because embedded Storyline 360 courses in a Rise 360 course are published to Review 360 format, and not in LMS format

I’ll be happy to pass your thoughts on to our product team, but you can also feel free to detail them more through a feature request!

Ian Davies

Thank you for the reply, but this sounds like a technical implementation limitation rather than something functional.  There should be no reason why a Rise course that reports xAPI statements to the LMS cannot also report the statements from an embedded Storyline block.  Both Storyline and Rise support passing xAPI statements to the LMS independently but not when used together, and a Storyline feature that stops working when it is used in conjunction with another one of your products seems like a bug or an implementation limitation rather than it being designed to work this way.

Can you please pass my comments on?  If this is still considered a feature request then I will happily submit a feature request using the link you supplied.

Jose Tansengco

Hi Ian, 

We appreciate the feedback! When you publish a Storyline 360 course for LMS distribution, certain files are included in the published output which allows the course to work in an LMS. These files, like the SCORM Driver, are not present when you publish a course to Review 360 (which is what is used to embed a Storyline 360 project as a block in a Rise 360 course).

We suggest raising the feature request so our product team can review your thoughts on how the feature can be improved. Here's a quick look at how we manage feature requests for your reference.