7 Replies
Cheng Li

Adrian Dean said:

Hi Cheng,

Sorry to hear about your issue. Please take a look at the following and see if it helps.

Always Happy to Help,

Adrian


Hi Adrian,

Is there a way to test out the reason for the trigger not working properly? I have followed the methods in the link you gave me, but the trigger still doesn't work. 

Is it possible because I run the published course on my local drive?

Thanks,

Cheng

Cheng Li

Adrian Dean said:

Hi Cheng,

Yes, that is correct. If you'll look at the Local Content section of the link I provided, there are a lot of local security restrictions that may keep the Exit Course trigger from working. If you need a place to host your content for testing, check out: http://tempshare.articulate.com/

-Adrian


Problem solved! Thanks a lot, Adrian!

Regards,

Cheng

Ashley Terwilliger

Hi Jon,

You're following the steps outlined below? Did you try the last line as well? 

If the Exit course trigger still doesn't work after uploading the course to your LMS, try the following:

It's strongly recommended that you create a backup of the Configuration.js file prior to modifying it as described below.

  1. Locate the Configuration.js in the following directory, depending on your version of Windows:
    • 32-bit Windows:  C:\Program Files\Articulate\Articulate Storyline\Content\lms
    • 64-bit Windows:  C:\Program Files (x86)\Articulate\Articulate Storyline\Content\lms
  2. Open the Configuration.js file in a text editor, such as Notepad.
  3. Change this line: var EXIT_BEHAVIOR = “SCORM_RECOMMENDED”;

    To: var EXIT_BEHAVIOR = “ALWAYS_CLOSE”;
  4. Republish your course.

If it still doesn't work, try changing the line in step 3 to: var EXIT_BEHAVIOR = “ALWAYS_CLOSE_TOP”;

You may also want to test it within SCORM Cloud, and if the Exit course trigger works there, with or without the modification above, I'd suggest connecting with your LMS team.