Triggers and player tabs that exit the course won't work in Review 360, so what you're seeing is expected. However, they'll work in browsers that allow tabs to close programmatically when your published output is hosted on a web server or LMS.
Since the exit course button isn't working after uploading your course to your LMS, please try these steps listed below:
Depending on your versions of Storyline and Windows, find the Configuration.js file in the following directory. If you're using Storyline 360, you'll find the scormdriver.js file in the same directory. Then proceed to the next step.
1 Reply
Hello Camille,
Triggers and player tabs that exit the course won't work in Review 360, so what you're seeing is expected. However, they'll work in browsers that allow tabs to close programmatically when your published output is hosted on a web server or LMS.
Since the exit course button isn't working after uploading your course to your LMS, please try these steps listed below:
Configuration.jsfile in the following directory. If you're using Storyline 360, you'll find thescormdriver.jsfile in the same directory. Then proceed to the next step.Storyline 360
32-bit Windows:
C:\Program Files\Articulate\360\Storyline\Content\lms
64-bit Windows:
C:\Program Files (x86)\Articulate\360\Storyline\Content\lms
scormdriver.jsfile and/or theConfiguration.jsfile in a text editor, such as Notepad.var EXIT_BEHAVIOR = “SCORM_RECOMMENDED”;var EXIT_BEHAVIOR = “ALWAYS_CLOSE”;If it still doesn't work, try changing the line in step 4 to:
var EXIT_BEHAVIOR = “ALWAYS_CLOSE_TOP”;Please keep us posted and let us know if you have additional questions!
This post was removed by the author