Attestation at the end of each scene

Feb 27, 2023

Hi. I am creating a course that has 7 scenes. At the end of each scene, I would like an attestation that is reportable through the LMS that the scene was complete.  The learners do not need to complete every scene to "pass" the course. Different learners will need different scenes, some will need all scenes, some will only need a couple. I would like to be able to pull a report in the LMS to show who has completed which scenes.

I am struggling with the best way to do this.

Thank you for any suggestions!

8 Replies
Eric Schaffer

Not exactly sure what you are looking at but. If they pick a path on the first slide that is connected to a variable. Then the variable tells them which slides they need to look at. Each slide adds 1 to the variable. Then a final slide that counts the variable for their path tells the LMS they have completed the task. 

If you need help let me know.

Julian Rose

Hei there,

Are you able to distinguish an LRS (Learning Record Store) from an LMS? If so, a good way to capture progress would be through xAPI.

xAPI allows you to send custom statements to an LRS. This extends the SCORM "complete" or "passed" tracking events.  And would include the ability to record attestations at the end of a scene a series of slides for example. Or in fact, you can use xAPI to record any event at all that can be triggered. 

How To: In storyline, while editing a slide, if you look at the triggers that can be inserted, this includes "Send xAPI statement". And you can create a custom statement. 

And: You can send xAPI statements to an LRS whether you publish to a SCORM or to LMS/LRS or Web. But you cannot send xAPI when publishing to Review360. 

Warning: It is a bit technical.

Want to know more: 

Hope this helps

Walt Hamilton

A couple of thoughts on variables:

I got home last night, and the cat insisted he had not been fed all day, and was STARVING. I hadn't been there all day, so I didn't know, and my wife was off to her quilting party, so I couldn't ask her. Fortunately, she left a note on the counter that said "I fed the cat", so I knew not to feed him again.
The note she left me is the variable. I couldn't see her feed the cat, but I could see the note and know what went on while I was gone. Storyline is just like I was. One slide has no way of knowing what happens on another slide, but it can read a message left for it in a variable, and know what the learner did on another slide, provided you, the develope,r used those actions on that other slide to change the contents of a variable.
The cat got pretty insistent, so I gave him a snack, crossed out her message, and wrote, "He's also had a bedtime snack", and went to my meeting.
The note is the variable. Everybody can see it, and it never changes unless you, thedeveloper, create a trigger to change it.
My wife is getting older (I'm not, just she), and takes a bunch of medicines. She puts them in one of those little plastic gadgets with seven boxes. Every night, (if she remembers :) ) she looks in the box for that day. If it is empty, she knows she has taken her pills that day.
The pill box is the variable. She can't always remember everything, but if the box has pills in it, she knows to take them. 
Variables are designed to be seen everywhere, but not heard (much like small children of a previous generation).  SL cannot multi-task, so only one slide at a time can be active. SL has no memory, so when a slide  becomes active, it can't know what went on while it was hibernating. That's why variables were invented.  Each slide can look at the note (variable) and by seeing what is on there now, it can know what went on somewhere else, or some other time. I couldn't hear my wife write the note, but I can read it and know what went on at home while I was not there.