Capture text responses using built-in xapi functionality May 12, 2022 By Niall Banaghan Hi all, Is there a way to capture text responses using the in-built xAPI triggers in SL360? I know Devlin Peck has created awesome tutorials on achieving this using javascript but I wondered it there was a way using the available functionality in SL. Thanks in advance
Maria Costa-Stienstra Staff almost 2 years ago05/12/22 at 1:44 pm (UTC) Hi, Niall. Thank you for reaching out! We have an article on using xAPI statements to send the value of a variable to the LMS. Take a look below: Storyline 360: How to Send the Value of a Variable to an LMS/LRS - xAPI I hope this helps!
Niall Banaghan Author Maria Costa-Stienstra almost 2 years ago05/12/22 at 2:55 pm (UTC) Thanks for this, however, I'm testing in Scormcloud and cannot see it recording the entry. I have attached the simple test file below. Custom_xAPI_test.story
Maria Costa-Stienstra Staff almost 2 years ago05/13/22 at 4:09 pm (UTC) Hi, Niall. Thank you for sharing the .story file! I believe the issue is related to the id being blank on your statement, as I get an error when inspecting it (right-click>Inspect>Network>Fetch): I recreated the trigger using the default id: After re-publishing and uploading it to SCORM Cloud, I was able to receive the correct statement: Let me know if this helps!
Niall Banaghan Author almost 2 years ago05/17/22 at 8:30 am (UTC) This post was removed by the author
Niall Banaghan Author Maria Costa-Stienstra almost 2 years ago05/17/22 at 9:09 am (UTC) Works a charm, thanks Maria!
4 Replies
Hi, Niall.
Thank you for reaching out!
We have an article on using xAPI statements to send the value of a variable to the LMS. Take a look below:
I hope this helps!
Thanks for this, however, I'm testing in Scormcloud and cannot see it recording the entry. I have attached the simple test file below.
Hi, Niall.
Thank you for sharing the .story file!
I believe the issue is related to the id being blank on your statement, as I get an error when inspecting it (right-click>Inspect>Network>Fetch):
I recreated the trigger using the default id:
After re-publishing and uploading it to SCORM Cloud, I was able to receive the correct statement:
Let me know if this helps!
This post was removed by the author
Works a charm, thanks Maria!