Forum Discussion

ToddHaynes-40dc's avatar
ToddHaynes-40dc
Community Member
5 months ago

Exit Button - What SCORM command(s) sent?

We're trying to address the situation where our LMS is not tracking the session time a learner is in a course if they close the course using the browser's X button.

If learners close the course using a button with Storyline "Exit Course" trigger, time in session is tracked correctly with the LMS. Guess what? Leaners often skip this.

Anyone know the SCORM 2004 commands the Exit Course trigger executes?

SetReachedEnd, SCORM2004_Normal_Exit, lmsAPI.Setsession_time();, lmsAPI.SetExit(normal); , SCORM2004_CallTerminate()

Thanks in advance!

 

storyline 360
  • Nedim's avatar
    Nedim
    Community Member
    5 months ago

    The exit course trigger attempts to exit the course and close the browser window. Typically, it directs the end user back to the LMS. Now, when testing in SCORM Cloud, the session time is recorded regardless of whether the "Exit course" trigger is used or the X button is clicked. Have you tried testing your course in SCORM Cloud to see if the issue persists there?

  • ToddHaynes-40dc's avatar
    ToddHaynes-40dc
    Community Member
    5 months ago

    Yes we have.

    Course: 7 slides, has quiz, results slide is slide #5.

    SCORM Cloud:

    • if user exits the course on slide #7 by clicking the browser's close button, the session time is not recorded.
    • If the user clicks an exit button with an "Exit Course" trigger, the session time is recorded correctly.

    Therefore, I an assuming the Exit Course trigger is somehow posting the session time.

    • JoseTansengco's avatar
      JoseTansengco
      Staff
      5 months ago

      Hi Todd,

      Happy to help!

      You can enable the LMS debug mode for your course to see which events are logged right when you exit your course using the "Exit Course" trigger.

      There also isn't a fixed action associated with the "Exit Course" trigger. The behavior of this trigger is defined in the 'lms/scormdriver.js' file in the published output and can be modified according to your needs. 

      This section in the file is where you can specify the behavior of the trigger: 

      If you're comfortable using Javascript, you can also check out this community post where members shared Javascript solutions that modified the behavior of this trigger.